Allow for Python <4 versions

[RobPasMue]

When moving from pyproject.toml to setup.py, PyDPF-Core stopped supporting Python 3.11+ versions. In your previous setup.py file, your Python limitations were >=3.7, <4 and now they are >=3.7, <3.11. This will cause a conflict with the PyAnsys metapackage as we can tell from: https://github.com/pyansys/pyansys-dev/issues/4

I submit this PR to replicate the previous behavior you had. I understand that this change was unintended. Consider adding a Python 3.11 smoke test in your workflow as well =)

[codecov]

Codecov Report

Merging #773 (29e3ea5) into master (2fbf15c) will decrease coverage by 0.09%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #773      +/-   ##
==========================================
- Coverage   88.67%   88.59%   -0.09%     
==========================================
  Files          71       71              
  Lines        8114     8107       -7     
==========================================
- Hits         7195     7182      -13     
- Misses        919      925       +6     

[Revathyvenugopal162]

Thanks for solving this @RobPasMue .

[PProfizi]

Hey @RobPasMue, thanks for this change, although I do not think it was a mistake. We initially did not support 3.11 explicitly, hence the lack of testing. What I understand though is that pyansys packages should explicitly support 3.11 or at the very least allow it.
What I will do is merge this PR so we do not prevent the pyansys metapackage CI from passing, yet I will also create an issue here to add explicit testing of 3.11. I am not fond of just doing smoke tests, so we usually test all Python versions we are supposed to support. We should most likely move to running only examples though.

[RobPasMue]

Hey @RobPasMue, thanks for this change, although I do not think it was a mistake. We initially did not support 3.11 explicitly, hence the lack of testing. What I understand though is that pyansys packages should explicitly support 3.11 or at the very least allow it. What I will do is merge this PR so we do not prevent the pyansys metapackage CI from passing, yet I will also create an issue here to add explicit testing of 3.11. I am not fond of just doing smoke tests, so we usually test all Python versions we are supposed to support. We should most likely move to running only examples though.

Oh great then. Yeah, we are avoiding explicit disregard of Python 3.11 - at least allow it even if you are not sure if it works perfectly fine or not. If you intend on testing all the Python versions you support that's even better :)