fix: state upperbound (3.12) for python version support

[amarsjac]

Fixes: #493

What was the problem/requirement? (What/Why)

Dependencies required for the library do not exist for python 3.13

What was the solution? (How)

put in version cap into pyproject.toml file to prevent pip installing on python 3.13

What is the impact of this change?

Users will no longer be able to pip install the library if python version is >=3.13

How was this change tested?

hatch build

Was this change documented?

• Are relevant docstrings in the code base updated?
• Has the README.md been updated? If you modified CLI arguments, for instance.

Does this PR introduce new dependencies?

This library is designed to be integrated into third-party applications that have bespoke and customized deployment environments. Adding dependencies will increase the chance of library version conflicts and incompatabilities. Please evaluate the addition of new dependencies. See the Dependencies section of DEVELOPMENT.md for more details.

• This PR adds one or more new dependency Python packages. I acknowledge I have reviewed the considerations for adding dependencies in DEVELOPMENT.md.
• This PR does not add any new dependencies.

Is this a breaking change?

yes this removes pip support for python 3.13

Does this change impact security?

no

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud