Centralize TFM infrastructure

[hoyosjs]

No description provided.

[tommcdon]

It looks like SupportedSubrocessNetTargetFrameworks might contain a typo. Perhaps SupportedTargetFrameworks might work?

[mikem8361]

I agree with Tom about SupportedSubrocessNetTargetFrameworks. Either Subrocess -> SubProcess or something like Tom suggested

[am11]

Is it intentional? My understanding is that source-build cares less about netstandard compat than non-sourcebuild (which only matters if we want .net framework compat; name of this project suggests otherwise; .NETCore.Client).

[hoyosjs]

NETCore.Client needs to support the lowest .NET version (net6.0) - sourcebuild has trouble with this since it doesn't have the 6.0 refpack available always.

[am11]

IOW, who will be affected by:

Suggested change

	<TargetFrameworks Condition="'$(DotNetBuildSourceOnly)' != 'true'">netstandard2.0;$(NetCoreAppMinTargetFramework)</TargetFrameworks>
	<TargetFramework Condition="'$(DotNetBuildSourceOnly)' == 'true'">netstandard2.0</TargetFramework>
	<TargetFramework>$(NetCoreAppMinTargetFramework)</TargetFramework>

[hoyosjs]

We are - and sourcebuild would. A lot of what lives in this repo is sadly stuck either in NS or has to be dual target. It also has to target the lowest netcoreapp version we have in support. And SB doesn't like that last bit - hence this.