Add branch protection rules and update GitHub workflow configurations

[jfrench9]

Summary

This PR introduces branch protection rules for main and release branches while updating GitHub workflow configurations to improve repository governance and CI/CD processes.

Key Accomplishments

Branch Protection Rules

• Main Branch Protection: Added comprehensive protection rules including required status checks, pull request reviews, and merge restrictions
• Release Branch Protection: Implemented specialized protection rules for release branches to ensure stable release processes

Workflow Configuration Updates

• Updated Claude workflow with additional configuration
• Refined create-pr workflow settings for better integration
• Enhanced tag-release workflow with improved triggering and execution logic
• Modified test workflow configuration for optimized performance

Infrastructure Considerations

• Branch protection rules will be enforced automatically once merged, affecting how code is merged into protected branches
• Workflow changes may impact existing CI/CD pipelines and automation processes
• Teams should be aware of new merge requirements and approval processes

Breaking Changes

• Merge Process: Direct pushes to main and release branches will be restricted
• Review Requirements: Pull requests may now require specific approvals before merging
• Status Checks: Certain workflows must pass before merging is allowed

Testing Notes

• Workflow configurations have been updated to align with new branch protection policies
• Existing automation should continue to function with the updated workflow triggers
• Monitor initial merges to ensure protection rules work as expected

This change strengthens the repository's development workflow while maintaining compatibility with existing processes.

---

🤖 Generated with Claude Code

Branch Info:

• Source: refactor/workflow-job-updates
• Target: main
• Type: feature

Co-Authored-By: Claude noreply@anthropic.com