Bug: Client x-request-id Mangled by RequestIdExtension

**Summary**
Recently we have noticed that this [Envoy issue](https://github.com/envoyproxy/envoy/issues/11532) might affect App Mesh’s customer as well. While Envoy is working on a fix to mitigate this issue. We want to create an issue on our side to track what changes will be required on App Mesh’s side to enable the mitigation

**Context**
Envoy uses the 14th byte of a UUID in the `x-request-id` header to indicate a tracing decision. For cases where the `x-request-id` header is externally injected (rather than have it injected by Envoy), Envoy will modify the UUID 14th byte.
This modification results in a different UUID than the one provided by the caller and break the `x-request-id` passed along a call chain.

**Next Steps**
App Mesh will track the status of this issue in Envoy, once Envoy released the fix to mitigate this issue we will take corresponding actions on our side ASAP.