[WIP] Create a workflow for version release management

[Copilot]

Thanks for assigning this issue to me. I'm starting to work on it and will keep this PR's description up to date as I form a plan and make progress.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Create a Release workflow</issue_title>
<issue_description>Create a workflow that:

1. Creates a $version var that holds the version metadata for the project, minus any suffixes identifying it as a dev version (e.g., .dev, -SNAPSHOT)
2. Creates a release branch, release/$version
3. On the release branch, update the version metadata to $version
4. Create a $tag var that contains tag/$version in anticipation of creating a GIT tag for this version
5. Update any links to GitHub in README.md to point to the release tag branch
6. Create a tag for the release, and a bugfix branch, from the release branch
7. Create a GitHub release
8. On the main branch, iterate the minor version number</issue_description>

<agent_instructions>Create a straightforward usage guide that explains what the extension does and how to use it. Avoid hyperbole and marketing terms, and use UK english.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Create a Release workflow #3

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[minouris]

Retry, please

[minouris]

@copilot Reject all reviews, and retry