fix(ci): standardize poetry version key in CI configuration files

[riordache12]

Description

• replaced branch-names or versions with their respective hashes

• changed poetry-version to version

• Fixes Fix the ci warnings and replace the branch names with hashes #1174

Check relevant points.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• Pipeline is passing

Checklist:

Prepare items below using:
[ ❌ ] (markdown: [ :x: ]) for TODO items
[ ✅ ] (markdown: [ :white_check_mark: ]) for DONE items
[ N/A ] for items that are not applicable for this PR.

• updated version number in setup.py/pyproject.toml/environment.yml.
• updated the lock file.
• added changes to History.rst.
• updated the latest version in README file.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• documentation are updated.

[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