feat: implement industry-standard tag-based release workflow

[doughayden]

Summary

Implements tag-based release workflow (industry standard) to resolve branch protection conflicts with semantic-release.

Key Changes

• Tag-only releases: Creates semantic version tags without modifying repository files
• No version file tracking: Removes version_toml and version_variables from config
• Protected branch compatible: No commits pushed back to main branch
• Simplified permissions: Only requires contents: write for tag/release creation
• Industry standard: Follows patterns used by React, Vue, Angular, and other major projects

Configuration Changes

semantic-release config:

[tool.semantic_release]
commit = false    # No version bump commits
push = false      # No pushes to main branch  
tag = true        # Create semantic version tags
vcs_release = true # Create GitHub releases

Workflow permissions:

permissions:
  contents: write  # For creating tags and releases
  id-token: write  # For OIDC token access

How It Works

1. Push to main triggers workflow
2. Semantic-release analyzes conventional commits
3. Creates version tag (e.g., v0.3.0)
4. Generates GitHub release with auto-generated notes
5. No repository modifications - main branch stays clean

Benefits

✅ Compatible with protected branches - no bypass needed
✅ Industry standard pattern - used by major open source projects
✅ Clean repository history - no automated version bump commits
✅ Full automation - tags and releases created automatically
✅ Conventional commits - semantic versioning based on commit messages

Testing Plan

• Merge this PR to main
• Verify workflow creates tag and release automatically
• Confirm no commits pushed back to main
• Validate GitHub release contains proper assets and notes

Resolves

• Closes fix: semantic-release Git push fails with branch protection #23 (Git push failures with semantic-release)
• Addresses branch protection compatibility issues
• Implements sustainable automated release process

🤖 Generated with Claude Code