feat: adjust set command to support version ranges

[CBeck-96]

Expand set to allow the processing for version ranges.

[github-actions]

Coverage Report •

File	Stmts	Miss	Cover	Missing
__main__.py	323	20	93%	217–218, 235, 245, 664–665, 669–674, 676, 679, 689–692, 696, 861
set.py	197	37	81%	56–59, 78–86, 88–89, 91–94, 105, 196–197, 200, 202, 205, 209, 213–217, 236, 264, 273, 304, 307, 334
TOTAL	1677	91	94%

Tests	Skipped	Failures	Errors	Time
295	2 💤	0 ❌	0 🔥	4.922s ⏱️

[mmarseu]

I suggest you don't attempt to invent your own version range syntax. There are smarter people than us working on that sort of thing and they came up with existing solutions, which additionally fit nicely into the CycloneDX ecosystem. Primarily, purl's proposed version range specification comes to mind:

• Proposal
• Experimental implementation

It is already being referenced by CycloneDX

This would largely render version_processing.py obsolete and therefore cuts down the code in this PR by more than half. Its always great to have less code to maintain!

[mmarseu]

This is a lot better than the last attempt. Good job!
A few comment remain but mostly minor stuff.

[mmarseu]

Is it intentional, that a version range cannot be set via the command-line, only using the --from-file option?

[mmarseu]

Almost good to go!

[CBeck-96]

Is it intentional, that a version range cannot be set via the command-line, only using the --from-file option?

It was not...

[italvi]

@CBeck-96 please change the flag according to our guidelines and adjust your example, so that everybody understands when the version_range would apply or not, as otherwise everybody would be required to read the univers-specification.

Further, please check if the use of the term "schema" is really required or you could stick to only use "range".