Y24-020 Add relevant exchanges, queues, users, etc. to RabbitMQ for new Bioscan messages

[sdjmchattie]

User story
The required queues, exchanges and users will need to be added to RabbitMQ to be able to receive messages in a consumer.

Who are the primary contacts for this story
Stuart McHattie

Who is the nominated tester for UAT
PSD

Acceptance criteria
To be considered successful the solution must allow:

• A user is configured with permissions for writing messages to an exchange.
• A user is configured with permissions to read messages from the queue the exchange routes to.
• Exchanges are defined for deployment to the RabbitMQ instance:
  • One to receive dead letters for unprocessable messages.
  • One to receive unrouted message.
  • One that will receive messages from the first user above.
• Queues are defined for deployment to the RabbitMQ instance:
  • One to receive the messages sent to the main exchange with a dead letter exchange routing to the dead letter exchange above.
  • One to receive a second copy of messages sent to the main exchange for monitoring purposes.
  • One to receive dead letters.
  • One to receive unrouted messages.
• Bindings from exchanges to queue are defined for deployment to the RabbitMQ instance:
  • The unrouted exchange sends messages to the unrouted queue.
  • The main exchange for incoming operations routes to the main queue with a routing key appropriate for the operation.
  • The main exchange also routes messages to the monitoring queue.

Dependencies
This story is blocked by the following dependencies:

• We need access to the final enterprise managed RabbitMQ to do this work.

Additional context
It's not clear what the interface to the enterprise RabbitMQ is going to be at this point, so the approach taken might have to vary from that used for Heron and TOL, depending on what level of access we are given. Ideally this will be automated, but if we can't do that then we will have to trust that the enterprise RabbitMQ instance will never need to be reconfigured in future due to SLAs.

[sdjmchattie]

The following diagram captures the intended configuration of RabbitMQ for this use case: https://lucid.app/lucidchart/19d232be-c270-407f-94ee-820228f1ce06/edit?viewport_loc=121%2C-405%2C2529%2C1408%2C0_0&invitationId=inv_e889d760-c60b-49b2-8e69-dbaa098e8e96