Allow `component targets` to validate a binary in a semver-compatible manner

[julienvincent]

Currently the wasm-tools component targets command only allows validating that a component targets a specific world exactly. This means that all interface semver versions need to match one-for-one.

Some interfaces, such as WASI, only require the minor (0.2 vs 0.2.3) for compatibility. Additionally, some languages compile to different WASI interface versions depending on what subset of the stdlib is used. This makes it non-deterministic and impossible to consistently validate.

This is a feature request to allow specifying the semver compatibility requirement to use when validating target worlds.

Ideally this is done in a way where different compatibility requirements can be specified for different interfaces present in the target world. The WASI convention of allowing compatibility with the minor is not common to all WIT interfaces AFAIU. Meaning some interfaces might require strict semver version matching (not sure about this one though).

@alexcrichton Pinging you here as you seem to be the person driving this subset of behaviour - anything to add?

See original zulipchat discussion

[alexcrichton]

Nah makes sense to me, thanks for filing an issue! I won't have a chance to get around to this for awhile, but if anyone would like to get to this in the meantime I'd be happy to review a PR