chore: apply plugin version discipline

[intel352]

Part of GoCodeAlone/workflow#760.

Changes:

• keep committed plugin.json.version at the 0.0.0 development sentinel
• remove the obsolete sync-plugin-version workflow when present
• add post-build release validation so the shipped manifest is checked against the tag
• preserve/strengthen runtime capability checks where needed

Verification:

• wfctl plugin validate-contract .
• wfctl plugin validate-contract --for-publish --tag v9.9.9 .
• GOWORK=off go test ./...

[Copilot]

Pull request overview

Applies plugin-version discipline: keeps plugin.json at the 0.0.0 development sentinel, removes the auto-sync workflow that previously updated it on tag pushes, and adds a post-build validation step in the release workflow to ensure the shipped manifest matches the published tag.

Changes:

• Reset plugin.json version to the 0.0.0 development sentinel.
• Delete .github/workflows/sync-plugin-version.yml.
• Add post-build validate-contract --for-publish --tag --release-dir check in release.yml.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
plugin.json	Sets version to the 0.0.0 development sentinel.
.github/workflows/sync-plugin-version.yml	Removes the now-obsolete plugin.json version sync workflow.
.github/workflows/release.yml	Adds post-build validation that the shipped plugin.json carries the release tag.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.