moving to calendar versioning

[devsetgo]

Pull Request Description: Moving to Calendar Versioning

This pull request implements a transition to calendar versioning for our project. The motivation behind this change is to enhance clarity and consistency in our versioning scheme, aligning it with widely recognized semantic practices.

Key Changes:

• Updated the versioning format in dsg_lib/__init__.py and pyproject.toml to follow a calendar-based scheme (e.g., 2024.10.19.1).
• Adjusted the CI configuration to use the latest Python versions, ensuring compatibility with future releases.
• Enhanced documentation and badges in the README.md to reflect the new versioning approach and improve visibility of coverage and test status.
• Updated dependencies and scripts in pyproject.toml and requirements.txt to align with the new versioning logic.

Benefits:

• Improved Clarity: Calendar versioning provides immediate context regarding the release date, making it easier for developers and users to track the evolution of the software.
• Consistency: This approach minimizes confusion associated with traditional semantic versioning, particularly regarding major and minor version increments.
• Enhanced CI/CD Practices: By ensuring our CI/CD pipeline is aligned with the latest Python versions and dependencies, we are improving the reliability and robustness of our testing and deployment processes.

Overall, this change aims to streamline our development workflow and provide better versioning transparency for our users.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud