Consider "flighting" A/B customer paths that collect network traces

Lately, a handful of networking issues are preventing installation of runtimes via use of the install-scripts.
Example: https://github.com/dotnet/install-scripts/issues/380

Without network traces it is difficult to investigate the difference in install-script behaviors between their use in CI (which succeed) and in the extensions (which seem to fail regionally).

Enabling customers to opt in to collecting network traces would allow root-causing the issue, which currently result in a frustrating UX.