Ensure CLI Telemetry Logger is hooked up to all API-based MSbuild usage #51066
Description
Describe the bug
Today when users run CLI-based build commands (build, clean, pack, restore, etc) all builds that make it to MSBuild get a telemetry logger attached to them so that we can get build-time telemetry results for those builds.
API-based usage of MSBuild, which is prevalent for file-based apps, pre-build evaluations, etc, do not participate in this, which means we have an entire swath of usage that isn't being tracked in our unified way.
We need to provide a shim layer on top of all API-based usage of MSBuild for builds that injects/enables our logger in the same scenarios it does for non-API-based builds.