Fix version checks in SDK

[zhiltsov-max]

Motivation and context

• Added missing compatibility with micro- and smaller releases

How has this been tested?

Unit test

Checklist

• I submit my changes into the develop branch
• I have added a description of my changes into the CHANGELOG file
• I have updated the documentation accordingly
• I have added tests to cover my changes
• I have linked related issues (see GitHub docs)
• I have increased versions of npm packages if it is necessary
  (cvat-canvas,
  cvat-core,
  cvat-data and
  cvat-ui)

License

• I submit my code changes under the same MIT License that covers the project.
  Feel free to contact the maintainers if that's a concern.

[SpecLad]

I think this is slightly wrong, because it will calculate that 2.5.0a1 is compatible with 2.4.0. I would suggest something like this instead:

return current in packaging.specifiers.SpecifierSet(f"~= {target.epoch}!{target.major}.{target.minor}.{target.micro}")

[zhiltsov-max]

Yes, it's a nice catch.

Upd: it's better, but there is a problem with this approach, that

Version("2.1") in specifiers.Specifier(f"~= 2.1.pre1") -> True
Version("2.1.1") in specifiers.Specifier(f"~= 2.1.pre1") -> True
Version("2.1.1") in specifiers.Specifier(f"~= 2.1.0") -> True

Maybe it's not a big deal, but it doesn't look expected.

[SpecLad]

Since the version on the right side comes from the SDK, I wouldn't expect it to be a prerelease. And what's wrong with the 3rd case?

[zhiltsov-max]

I think, given what we do now (add the next release version to support the public instance, and once we publish it, we update SDK), it makes sense to try to limit the next version to its pre-release variant, so the old SDK will stop working automatically, once the new server release is deployed.

E.g.:
release 2.4
public server: 2.5.devX
sdk: v2.4 supporting >=2.4, <2.5

release 2.5
public server: 2.5
sdk v2.4 stops working