Dont use globals for the tc metrics settings

[matt-richardson]

Background

I had success all during testing for the metrics shipping, but as soon as I merged and used the prod one, it stopped working.

Interestingly, it started working after teamcity was restarted due to cluster upgrade. This suggests to me that the global was getting into a bad state due to concurrency.

This is wise anyway, as we want to avoid the use of the global properties, as it allows metrics per project.

[sc-96078]

Results

We now:

• no longer set the GlobalOpenTelemetry config
• add an attribute to the metric, so we can see what build it relates to this was done in Log build id with metrics #348.
• shutdown the metric reader, so that it doesn't leak threads

After

How to review this PR

Pre-requisites

• I have considered informing or consulting the right people
• I have considered appropriate testing for my change.

[akirayamamoto]

I am not familiar with this project but the idea of the change makes sense to me.
However, the (pair) return and the name of buildSpanProcessorAndMeterProvider sounds like could do with another class in there? Maybe "TelemetryProvider"? This class could have both the spanProcessor and the meterProvider. I haven't put much thought into the ideal solution. I am happy to merge as is though.