BAU: configure OpenTelemetry ID Generator

[whi-tw]

We need to use the XRay ID generator when using the XRay propagator, in
order to generate trace IDs in the correct format. As we're configuring
the propagator via the OTEL_PROPAGATORS environment variable, we can
gate the ID generator configuration behind the same variable to keep
things agnostic.

This can only be done via code, so we have to add this to the
OpenTelemetry SDK configuration in an initializer.
see: https://arc.net/l/quote/ctffkmlm

What problem does this pull request solve?

Trello card:

Things to consider when reviewing

• Ensure that you consider the wider context.
• Does it work when run on your machine?
• Is it clear what the code is doing?
• Do the commit messages explain why the changes were made?
• Are there all the unit tests needed?
• Do the end to end tests need updating before these changes will pass?
• Has all relevant documentation been updated?

[lfdebrux]

Please could you replace the link in the commit message with https://aws-otel.github.io/docs/getting-started/ruby-sdk/trace-manual-instr#instrumenting-an-application:~:text=Next%2C%20because%20the%20AWS%20X%2DRay%20ID%20Generator%20can%20only%20be%20configured%20through%20code%2C%20you%20cannot%20use%20an%20environment%20variable%20to%20select%20it.%20The%20ID%20Generator%20must%20be%20used%20at%20the%20time%20OpenTelemetry%20Ruby%20SDK%20is%20configured. so that the destination is transparent and recoverable if something happens to Arc/the AWS Otel docs? Thanks! 🙏

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

🎉 A review copy of this PR has been deployed! It is made of up two components

1. A review copy of forms-runner
2. A production copy of forms-admin

Important

Not all of the functionality of forms-runner is present in review apps.
Functionality such as sending emails, file upload, and S3 submission types are
deliberately disabled for the sake of simplifying review apps.

You should use the full dev environment to test the functionality which is disabled here.

It may take 5 minutes or so for the application to be fully deployed and working. If it still isn't ready
after 5 minutes, there may be something wrong with the ECS task. You will need to go to the integration AWS account
to debug, or otherwise ask an infrastructure person.

For the sign in details and more information, see the review apps wiki page.