Investigate migration to symbol.exe for symbol publishing

[hoyosjs]

• [ ] This issue is blocking
• [ ] This issue is causing unreasonable pain

This is something that will become increasingly common and might become a blocker at some point in the future. Originally, the .NET team wrote a symbol uploader tool since the ecosystem didn't handle MACHO, ELF, Dwarf, and other files. Nowadays, through collaborations with the 1ES team there's a symbol uploader cli that supports these scenarios. This tool will be the supported solution going forward as it's actively maintained to follow best security practices. This tool supports more modern authentication workflows and is maintained by the same team that supports the backends for the

There are a few things to consider:

• We'd have to explode nupkgs. The tool doesn't don't do this and has no practical reason to do so.
• Explore CLR related keys - dac/dbi/clr key combo.
• Full to portable PDB conversion is also not supported.

@epananth @mmitche

cc @mikem8361 @tommcdon @leculver

[hoyosjs]

cc: @markwilkie

[markwilkie]

Do you have any comments here @mikem8361 ?

[mikem8361]

Juan has covered the issues here. We really can't support the current symbol uploader going forward especially for authentication,

[hoyosjs]

@missymessa probably this shouldn't be in the "other teams" bucket. This will be a general infra requirement.

[missymessa]

Followed up with Juan offline. Leaving this in "tracking for other teams".