[WIP] Automate package.json version update during release workflow

[Copilot]

• Create a new GitHub Actions workflow for releases triggered by version tags
• Add version extraction step to strip 'v' prefix from tag
• Add step to update package.json version field
• Add git commit and push step for version change
• Add steps for building, packaging (.vsix), and attestation
• Test workflow configuration syntax
• Update documentation with release process

Original prompt

Automate version bump in package.json as part of the release workflow.

When a new version tag is pushed (e.g., v1.2.3), update the "version" field in package.json to match the tag (without the "v" prefix), commit the change, and push it back to the repository before packaging and attestation steps.

This ensures that the package.json version always matches the release tag, and the generated .vsix file has the correct version.

*This pull request was created as a result of the following prompt from Copilot chat.* > Automate version bump in package.json as part of the release workflow. > > When a new version tag is pushed (e.g., v1.2.3), update the "version" field in package.json to match the tag (without the "v" prefix), commit the change, and push it back to the repository before packaging and attestation steps. > > This ensures that the package.json version always matches the release tag, and the generated .vsix file has the correct version.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[jhaisley]

@copilot can you commit the workflow file?