Publish new component versions automatically after merging to main

[Y1hsiaochunnn]

Merging to main previously ran CI but never published a component because publication only supported manual dispatch from a pre-created version tag. Automatically publish each new manifest version after a successful full build matrix, then create its GitHub Release after the registry confirms the upload.

• Keep manual dry runs and tag-based retries. Skip automatic publication when the version already has a completed GitHub Release.
• Create the version tag on the validated commit and refuse to move an existing tag to different source. Fail on GitHub lookup errors instead of treating them as a missing release.
• Force complete release validation independently of ordinary changed-file routing. Keep registry credentials in the upload job and grant repository write access only to the tag/release jobs.
• Document version bumps, immutable publication, and recovery when uploading or GitHub Release creation fails.

Validation for 2e68d9b: 24 Python tests, seven release-operation tests, actionlint, catalog/navigation checks, and the full skill Markdown audit passed. All eleven local ESP-IDF builds and all PR Actions checks passed on this commit. The publication dry run also passed, including all eleven builds and authenticated registry validation; tag creation and GitHub Release were skipped as intended. Board source and component version remain unchanged; merging this workflow enables the initial 0.1.0 release.