Standardize GitHub Actions authentication to use GITHUB_TOKEN

[jfrench9]

Summary

This PR standardizes authentication across all GitHub Actions workflows by migrating from ACTIONS_TOKEN to the built-in GITHUB_TOKEN, simplifying setup and improving security.

Key Changes

• Authentication Standardization: Updated 11 workflow files to use GITHUB_TOKEN instead of custom ACTIONS_TOKEN
• Simplified Setup: Reduced complexity in bootstrap and setup scripts by removing custom token requirements
• Improved Documentation: Enhanced setup documentation for GitHub Actions secrets configuration
• Code Cleanup: Removed 33 lines of unnecessary configuration code across workflows

Benefits

• ✅ Simplified Onboarding: No longer requires manual creation of personal access tokens for basic workflows
• ✅ Enhanced Security: Leverages GitHub's automatically provided tokens with appropriate scoping
• ✅ Reduced Maintenance: Eliminates token expiration and rotation concerns for standard operations
• ✅ Consistent Configuration: Standardized authentication approach across all CI/CD pipelines

Breaking Changes

⚠️ Repository Setup Impact: Teams currently using ACTIONS_TOKEN will need to:

1. Remove the ACTIONS_TOKEN secret from repository settings
2. Ensure workflows have appropriate permissions configured
3. Re-run setup scripts if using automated repository configuration

Files Modified

• All workflow files in .github/workflows/ (11 files)
• Setup scripts: bin/bootstrap.sh and bin/gha-setup.sh

Testing Notes for Reviewers

• Verify all workflow files use consistent token references
• Check that setup scripts no longer reference ACTIONS_TOKEN
• Confirm documentation accurately reflects new setup process
• Test bootstrap script runs without token-related errors

Browser Compatibility

No browser compatibility impact - this is a CI/CD infrastructure change only.

---

🤖 Generated with Claude Code

Branch Info:

• Source: chore/cleanup-gha-auth
• Target: main
• Type: feature

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