workflow: always use version-bump branch for version updates

[jassem-manita]

Description

Fixes #(issue)

Type of Change

• 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)
• Documentation update
• Code refactoring
• Performance improvement
• Test improvements
• CI/CD changes

Changes Made

Testing

• All existing tests pass
• New tests added for new functionality
• Manual testing performed

Test Commands Run

pytest tests/
flake8 midna/ tests/
black --check midna/ tests/

Test Results

Code Quality Checklist

• Code follows the project's style guidelines (Black, isort, Flake8)
• Self-review of code completed
• Code is commented where necessary
• Docstrings added/updated (Google-style format)
• No new warnings generated
• Commit messages follow conventional commits format

Documentation

• README updated (if needed)
• CONTRIBUTING.md updated (if needed)
• Docstrings updated
• Comments added for complex logic

Breaking Changes

• None

Additional Notes

Screenshots (if applicable)

Checklist Before Merge

• PR title follows conventional commits format
• All CI checks pass
• Code reviewed by at least one maintainer
• Branch is up to date with main
• No merge conflicts

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!