Add pytest-benchmark

[purva-thakre]

Description

Related Issues

Closes #
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?

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

[purva-thakre]

@PietropaoloFrisoni Can you help me understand the errors I see with the backend unit test failures? https://github.com/eclipse-qrisp/Qrisp/actions/runs/29994466218/job/89164792736?pr=745#step:7:125

Should I just add a way to skip these in the benchmarking job? Or are they something that need to be fixed?

Edit: Never mind. It was my mistake.