Runtime instance cookie from advertise protocol is different than from GetProcessInfo command

[jander-msft]

The diagnostics server in the runtime reports its runtime instance cookie via the advertise protocol when it connects to a diagnostic tool that is in listening mode. The serialization of this runtime instance cookie occurs here.

The diagnostics server in the runtime as provides its runtime instance cookie via the GetProcessInfo command when an external tool issues this command via the diagnostic port. The serialization of this runtime instance cookie occurs here.

It seems that the cookie returned by the advertise protocol is partially different from the cookie returned from the result of the GetProcessInfo command.

An example of the difference of the values is:

Source	Value
Advertise protocol	cf3642da-628e-70b0-bfac-674c838fb60e
GetProcessInfo command	70b0628e-cf36-42da-bfac-674c838fb60e

I believe the issue is that the different sources serialize it differently and cause certain fields to be reordered incorrectly.

CC @dotnet/dotnet-diag @josalem

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

[josalem]

Whoops! Should be an easy fix. I'll have a PR up soon.