allow for different args with conduit > 12

[ssicard]

Description

Add compatibility for conduit 0.12 and 0.13 to accommodate updates in flags. This will allow for future conduit upgrades.

Quick checks:

• I have followed the Code Guidelines.
• There is no other pull request for the same update/change.
• I have written unit tests.
• I have made sure that the PR is of reasonable size and can be easily reviewed.

[lyuboxa]

I think these will be simpler defined using the tilde operator, e.g. ~0.11 will be the equivalent of >= 0.11, < 0.12 and then the equivalent for 0.12 as well

See https://github.com/Masterminds/semver?tab=readme-ov-file#tilde-range-comparisons-patch

[lyuboxa]

Small nitpick, if you change the key to the be the constraint, map[semver.Constraint]func()[]string)

you can essentially loop over

for rule, fn := range ... {
   if rule.Check(ver) {
      return fn() 
   }
}

[ssicard]

That strategy would throw a parse error, since I would still need to ignore the error that may be returned from NewConstraint. I could declare the constraints before making the map, but that wouldn't save lines

[lyuboxa]

Yea that is a good point, though the errs returned by parsing new version and constraints should be checked, anyway. Referring to NewVersion and NewConstraint, this will reduce the errors with typos in code.

You can setup the constraints in NewFlags and make them part of Flags and yea that will be a bit more work.

[lyuboxa]

Suggested change

	c, _ := semver.NewConstraint(rule)
	c, err := semver.NewConstraint(rule)
	if err != nil {
	return nil, fmt.Errorf("failed to parse constraint %q: %w", rule, err)
	}