Emit More EventSource Data For Metrics Measurements

[tarekgh]

Fixes #93097 and #93767

• MetricEventSource value published events don't resolve which scope they are refering to #93097
• MetricEventSource value published events don't unambiguously resolve which Meter and Instrument tags they are refering to #93767

This change enables the emission of additional metrics data during measurement publishing. Specifically, it will emit the instrument's formatted tags and hash, as well as the meter's formatted tags, scope hash, and meter hash. With this extra data, aggregators can easily differentiate between instruments created with identical parameters such as name, tags, and units. Similarly, it allows for distinguishing between meters created with the same parameters, such as meter name, version, tags, and scope.

[tarekgh]

/azp run runtime-libraries-coreclr outerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[noahfalk]

A few suggestions inline

[noahfalk]

@wiktork @jander-msft - heads up since dotnet-monitor probably wants to consume this data too. Unless we get some extension the checkin deadline is the end of the week so this is likely to go fast.

[tarekgh]

/azp run runtime-libraries-coreclr outerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[tarekgh]

@noahfalk I have updated the code according to our offline discussion with introducing the instrument Id in our emitted events. If you are interested in looking at the update, please look at the last commit. Thanks!

[noahfalk]

LGTM!