I would suggest creating a comprehensive technical requirements document that addresses the following key areas before proceeding with this implementation:

Impact Analysis Document:

Detailed assessment of changes required in existing applications (ASP, Receiver, Data Processor, etc.)

Migration strategy from RabbitMQ-based Celery framework to Pub/Sub

Backward compatibility requirements and breaking changes

Technical Design Document:

Generic messaging interface specification

Message format compatibility between AMQP and Pub/Sub

Worker management and task routing strategy

Error handling and retry mechanisms

Performance and cost comparison analysis

Implementation Plan:

Evaluation of the 7.2 branch's improved connection logic as a foundation

Proof-of-concept development approach

Testing strategy (especially given the current blocker of no GCP environment)

Phased rollout plan

Operational Considerations:

Monitoring and observability changes

Development environment setup (Pub/Sub vs RabbitMQ)

Deployment and configuration management updates

I recommend scheduling a technical review session with the wider engineering team to:

Validate the requirements and approach

Gather feedback on potential implementation challenges

Ensure alignment on the migration strategy

Establish success criteria and acceptance tests