Refactor GitHub Actions workflows with dynamic image tags

[jfrench9]

Summary of Changes

This PR refactors our GitHub Actions deployment workflows to use dynamic image tagging, improving our CI/CD pipeline efficiency and maintainability. The changes streamline the deployment process by:

• Updated GitHub Actions workflows: Modified both production and staging workflow files to support dynamic Docker image tagging
• Simplified setup script: Significantly refactored bin/gha-setup.sh, reducing complexity by ~137 lines while maintaining functionality
• Enhanced deployment flexibility: Dynamic image tags allow for better version tracking and rollback capabilities

Key Infrastructure Improvements

• ✅ Dynamic Image Tagging: Workflows now generate image tags based on Git context (commit SHA, branch, or tags)
• ✅ Reduced Script Complexity: Streamlined setup script removes redundant code and improves maintainability
• ✅ Consistent Deployment Process: Unified approach between staging and production environments
• ✅ Better Version Control: Enhanced traceability of deployed versions through semantic tagging

Breaking Changes

⚠️ Deployment Process Changes:

• Teams using manual deployment processes may need to update their procedures
• Existing deployment scripts that rely on static image tags will need to be updated
• Docker registries may require cleanup of old static-tagged images

Testing Notes for Reviewers

CI/CD Pipeline Testing

• Verify staging deployment workflow triggers correctly on feature branch pushes
• Confirm production deployment workflow activates on main branch merges
• Test image tag generation with different Git contexts (commit, branch, tag)
• Validate that the setup script executes without errors in clean environment

Deployment Verification

• Check that generated image tags follow expected naming conventions
• Ensure rollback procedures work with new dynamic tagging system
• Verify environment-specific configurations remain intact

Browser Compatibility Considerations

This change affects backend infrastructure only and has no direct impact on browser compatibility. The application's frontend functionality remains unchanged, maintaining support for all previously supported browsers and devices.

Additional Notes

• No database migrations required
• No environment variable changes needed
• Existing Docker images remain functional during transition
• Consider running a test deployment to staging before merging to validate the new workflow

---

🤖 Generated with Claude Code

Branch Info:

• Source: refactor/improved-deployment
• Target: main
• Type: feature

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