Add globalJson property for global.json state to toplevelparser/command event

[elinor-fung]

Including the state of global.json in telemetry events for SDK commands.

• Update hostfxr bindings for hostfxr_resolve_sdk2 for global.json state added in Report invalid global.json state in dotnet --info and hostfxr_resolve_sdk2 runtime#118418
• Determine global.json state before emitting telemetry event for SDK command invocation - call into hostfxr to determine global.json state per Add telemetry for invalid global.json when running a command #50058 (comment)
• Include global.json state as a globalJson property in toplevelparser/command event

Resolves #50058

cc @dotnet/appmodel @AaronRobinsonMSFT @richlander

[elinor-fung]

@dotnet/dotnet-cli Is there a good way to locally view the telemetry events that actually get sent? I debugged through to make sure the event is created with the new property, but I don't know how to test beyond that.

[dsplaisted]

LGTM. It seems like this is adding a separate event for the global.json state, I'm not sure if that's best or if it would be better to add the global.json state to an existing event.

@baronfel can probably suggest how you can validate the telemetry sent locally.

[elinor-fung]

It seems like this is adding a separate event for the global.json state, I'm not sure if that's best or if it would be better to add the global.json state to an existing event.

My intent was to add a property to an existing event (toplevelparser/command). I believe that is what this is doing by adding to the properties of the ApplicationInsightsEntryFormat that gets created, but I could be confused.

[baronfel]

@elinor-fung's glomming onto the toplevelparser/command event correctly, it's just a bit weird of a semantic that we have there. I don't really like it, but we haven't revamped it yet.

you basically can't easily verify the telemetry locally. when we add Otel that will change and it'll become trivially verifiable, but that won't happen until after 10 GA sometime.

[baronfel]

Once a new build comes out we can check the GDPR classifications for this new data point. We'll need to add it to the existing telemetry docs.

[marcpopMSFT]

Once a new build comes out we can check the GDPR classifications for this new data point. We'll need to add it to the existing telemetry docs.

@baronfel I've done the classification. Who owns doing the documentation?