Enable python 3.13 in the ci pipeline

[NedislavKolev]

Description

Updated the workflow to run tests on Python 3.11 for PR builds and reserved full Python 3.11, 3.12, 3.13 test coverage for pushes to main.

Related Issues

Closes #823
Related to #

Type of Change

• Feature (new functionality)
• Change Request (modification of existing functionality)
• Bug Fix
• Refactoring (no behavior change)
• Performance improvement
• Documentation
• CI / Build

Breaking Change?

• Yes
• No

If yes, describe the impact and migration path:

What was changed?

• On main the workflow runs the tests on Python versions 3.11, 3.12, 3.13
• On PRs, the workflow runs the tests on Python version 3.11

How was it tested?

Test-ID	Status
T-001	✅ / ❌
T-002	✅ / ❌
T-003	✅ / ❌
T-004	✅ / ❌

Screenshots / Output (if applicable)

Checklist

• My code follows the project's coding standards
• I have performed a self-review
• I have added/updated tests (referencing issue Test-IDs)
• All tests pass locally and in CI
• I have updated the documentation
• I have added a changelog entry to changelog-dev.rst
• Breaking changes are documented with migration path

Reviewer Notes

I omitted Python 3.13 from the coverage.yml workflow to avoid redundant setup and wasted CI resources, as multi-version Python testing is already handled by our main test workflow.

[purva-thakre]

Since we want to test the workflows work as expected first before merging, temporarily enable them on the PR. Once the PR is close to merging, we can change the trigger and then merge.