ci: avoid hardcoding the branch name in publish.yml

[EchoEllet]

Description

Avoid hardcoding the branch name (master) in publish.yml to allow publishing a pre-release of release/v11

Previously, I hardcoded the branch name master to fix a CI failure and left a TODO in the publish.yml since we didn't need to publish a release from a branch other than master and it's also not a priority and I wanted to focus on other issues.

This allows maintainers to publish a release from any branch.

Type of Change

• ✨ New feature: Adds new functionality without breaking existing features.
• 🛠️ Bug fix: Resolves an issue without altering current behavior.
• 🧹 Code refactor: Code restructuring that does not affect behavior.
• ❌ Breaking change: Alters existing functionality and requires updates.
• 🧪 Tests: Adds new tests or modifies existing tests.
• 📝 Documentation: Updates or additions to documentation.
• 🗑️ Chore: Routine tasks, or maintenance.
• ✅ Build configuration change: Changes to build or deploy processes.