Move *EndpointInfo implementations to dotnet-monitor.

[jander-msft]

The collection rule system will hook directly into the ServerEndpointInfoSource (and eventually, the ClientEndpointInfoSource), so this class needs to move to the dotnet-monitor project. This means that the unit tests for these types need to move to a new unit test assembly for dotnet-monitor (this unit test assembly already exists in the feature/triggers branch, but I'm bringing it to the main branch). As part of this, I've refactored entry point assembly path calculation for the tests into a common helper since I needed to changed some of the ServerEndpointInfoSource tests into theories with each supported TFM.

Overview of changes:

• Move *EndpointInfo implementations to dotnet-monitor.
• Add dotnet-monitor unit test assembly and move *EndpointInfo tests to it.
• Consolidate calculating entry point assembly path into single utility method.

[kelltrick]

My suggestion here would be to move all the things necessary to add net7.0 into as few files as possible. Ideally all in TargetFrameworkMoniker.cs and the DotNetHost.cs.template + GenerateDotNetHost.targets

[jander-msft]

My suggestion here would be to move all the things necessary to add net7.0 into as few files as possible. Ideally all in TargetFrameworkMoniker.cs and the DotNetHost.cs.template + GenerateDotNetHost.targets

I'll see what I can do. If it requires iteration over a collection of the supported TFMs, then it might be be doable in the non-trivial case without writing a source generator. At the very least, I should be able to consolidate all TFM related logic into one manually written file.

[jander-msft]

My suggestion here would be to move all the things necessary to add net7.0 into as few files as possible. Ideally all in TargetFrameworkMoniker.cs and the DotNetHost.cs.template + GenerateDotNetHost.targets

All conversion methods have been made into extension methods in the TargetFrameworkMoniker.cs file. So if you go to add a new enum value, it's more obvious what needs to be updated.

Also, I've moved the notion of the BuildTargetFrameworkMoniker directly into the DotNetHost.cs file and used preprocessing to determines it value. This will cause a build failure if a new TFM is added to the project but is forgotten to be added to the enum and updating this static property.