Replace semver with packaging

[rashidakanchwala]

Description

Should we replace semver.Version with packaging.version.Version as PEP 440 versions are not exactly compatible with SemVer ?

https://peps.python.org/pep-0440/#semantic-versioning, https://packaging.pypa.io/en/stable/version.html

@astrojuanlu to provide more info.

Checklist

• Include labels so that we can categorise your feature request

[astrojuanlu]

This is a low-effort, low-gain ticket. Theoretically, there could be a Kedro version string that cannot be parsed by semver, which can nonetheless be parsed by packaging.version. The reason is that versions for Python packages uploaded to PyPI follow PEP 440, which has some incompatibilities with the SemVer spec.

More:

• Parse PEP440 versions python-semver/python-semver#395
• https://python-semver.readthedocs.io/en/latest/advanced/convert-pypi-to-semver.html

So, making the change is trivial, but also the advantages are mostly theoretical at this point.

[astrojuanlu]

More info on the specific features of Python versioning https://sethmlarson.dev/pep-440?date=2023-08-03

[tynandebold]

Closing this based on @astrojuanlu's comment.

[rashidakanchwala]

Opening this because we are using packaging now in backend so we might as well replace semver with packaging
cc - @noklam