custom versioning definition per meta-package

Would it be possible to allow a meta-package (for lack of a word for a packages versionless presence) to specify a custom versioning algorithm, so that rez-env's don't pull in things that aren't actually correct per the general rez algorithm?
Example being Foundry products, where 9.0v1b8 is considered newer than 9.0v1, when the b8 is the beta token for the version-that-will-be-9.0v1-in-the-future.

I'm not sure how one would represent that honestly, but a feature request nonetheless.

The issue names no files, tests, or entry points. Start by locating rez-env's version-resolution logic and the representation of meta-packages, then clarify how a package-specific algorithm should be configured. Done means the Foundry example resolves 9.0v1b8 and 9.0v1 according to the requested semantics without pulling incompatible packages.

Written by the indexing model from the issue text.