[TRI-5390] Ignore any `OTEL_` env vars users set (they mess up our tracing/logging)

[matt-aitken]

It's currently possible for users to to set the OTEL_ env vars when deploying, like OTEL_EXPORTER_OTLP_ENDPOINT and OTEL_EXPORTER_OTLP_HEADERS.

This is mostly when using our sync env vars extensions.

This messes things up because we need these to be set to specific values and the user provided ones are overriding ours. The result is that no logs get sent to us and the Run page is empty.

Fix

Ignore any env vars starting OTEL_, I think we already have an array of env vars to ignore. Don't throw an error because it will make the sync script painful for users.

_TRI-5390

[siddharthsharma94]

Had this exactly happen here, and explained my findings in the issue!

[matt-aitken]

We now ignore these env vars. We don't allow you to set them from now on, and they don't get loaded onto the machines when we execute runs