Use `MSH-11` to identify test messages in staging and production environments

[basiliskus]

DevEx/OpEx

After an internal discussion, we decided MSH-11 (ProcessingId) is the right candidate to identify two types of test messages: automated/scheduled and manually triggered. Following to the HL7 specs, we decided to use T (Training) for manual tests and N (Non-Production Testing) for automated tests.

Tasks

• [x] Update TI test files to use either T, D or N in MSH-11
  • T: test files to be sent to partners and sent manually
  • D: test files not to be sent to partners and sent manually
  • N: test files not to be sent to partners and sent by scheduled task
• [x] Update RS org settings to route test messages
• [x] Make sure RS accepts the values we plan to use for MSH-11
• [x] Remove workaround to rewrite MSH in hurl script
• [x] Add documentation in readme
• [x] Add documentation in ADR
• [x] Update routing settings in staging
• [ ] Ask Ott to update routing settings in prod

Additional Context

Add any other context or screenshots about the work here.

[basiliskus]

I'm waiting for feedback from SMEs to decide on the routing filters for MSH-11 to use in production