feat: enhance CI/CD workflows and remove lock file tracking

[jfrench9]

Summary of Changes

This PR introduces significant improvements to our CI/CD infrastructure and dependency management:

🔧 Workflow Enhancements

• Added branch protection rules for main and release branches with comprehensive configuration
• Updated GitHub Actions workflows across multiple files (claude.yml, create-pr.yml, tag-release.yml, test.yml)
• Improved CI/CD pipeline reliability and consistency

📦 Dependency Management

• Removed package-lock.json from repository to avoid lock file conflicts in collaborative development
• Updated .gitignore to exclude lock files (package-lock.json, yarn.lock, pnpm-lock.yaml)
• Enables flexible package manager usage across development environments

Key Improvements

• ✅ Enhanced branch protection with automated rules for critical branches
• ✅ Streamlined workflow processes with updated action configurations
• ✅ Reduced merge conflicts by excluding lock files from version control
• ✅ Improved developer experience with flexible dependency management

Breaking Changes

⚠️ Dependency Management Changes:

• Developers will need to run npm install, yarn install, or pnpm install after pulling these changes
• Lock files will be generated locally based on individual development environments
• Ensure consistent Node.js versions across team members to maintain dependency compatibility

Testing Notes for Reviewers

GitHub Actions Testing

1. Verify that all workflow files pass syntax validation
2. Check that branch protection rules are properly configured
3. Test workflow triggers on sample branches/PRs

Dependency Installation

1. Delete existing node_modules and lock files locally
2. Run fresh npm install (or preferred package manager)
3. Verify application starts and builds successfully
4. Confirm no missing or conflicting dependencies

Branch Protection Validation

1. Test that new branch rules prevent direct pushes to protected branches
2. Verify PR requirements are enforced correctly

Browser Compatibility Considerations

No direct browser compatibility impacts from these infrastructure changes. However:

• Ensure dependency updates don't introduce browser compatibility regressions
• Test application functionality across target browsers after fresh dependency installation
• Monitor for any version conflicts in browser-specific polyfills or dependencies

Additional Notes

This refactor sets the foundation for more robust CI/CD processes and reduces friction in collaborative development by eliminating lock file conflicts while maintaining dependency integrity through proper branch protection and workflow automation.

---

🤖 Generated with Claude Code

Branch Info:

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

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