Microsoft.NET.Workload.Emscripten prebuilts reported in latest builds

[MichaelSimons]

Microsoft internal CI - https://dev.azure.com/dnceng/internal/_build/results?buildId=2139238&view=logs&j=941f2e24-48a0-594a-6b1a-0e16aaeb8606&t=cffff4a5-f52c-50c6-45c9-52a0bd619b26

The following Microsoft.NET.Workload.Emscripten prebuilts are being detected in the latest CI builds:

/vmr/repo-projects/Directory.Build.targets(676,5): warning : Microsoft.NET.Workload.Emscripten.Current.Manifest-8.0.100-preview.3.8.0.0-preview.3.23167.1 [/vmr/repo-projects/dotnet.proj]
/vmr/repo-projects/Directory.Build.targets(676,5): warning : Microsoft.NET.Workload.Emscripten.net6.Manifest-8.0.100-preview.3.8.0.0-preview.3.23167.1 [/vmr/repo-projects/dotnet.proj]
/vmr/repo-projects/Directory.Build.targets(676,5): warning : Microsoft.NET.Workload.Emscripten.net7.Manifest-8.0.100-preview.3.8.0.0-preview.3.23167.1 [/vmr/repo-projects/dotnet.proj]

Checking the build logs I verified that a Microsoft.SourceBuild.Intermediate.emsdk 8.0.0-preview.3.23167.1 is being produced. The one thing that jumped out at me if the version of the prebuilt being loaded is rather strange - 8.0.100-preview.3.8.0.0-preview.3.23167.1

[MichaelSimons]

By analyzing the builds to identify when this regression was introduced, the following sha diff appear to be the source - https://github.com/dotnet/emsdk/compare/352d64e0ce9b99a8cff6207621432a986920ffd9..25d9f7a5e38a2d61b94ff341bc0d32135fcb15f9

[MichaelSimons]

I confirmed that the TFM filtering is the source of the prebuilts. I created a patch to revert the filtering for preview.3.

@NikolaMilosavljevic - Can you please investigate the underlying issue? TIA

[MichaelSimons]

Reopening to ensure the tfm filtering problem is addressed.