Update source-build prebuilts and test baselines

[MichaelSimons]

This should get a lot more of the internal CI legs to pass.

[MichaelSimons]

@mthalman - this appears to be showing the same CI failure symptoms that #15495 addressed. Any ideas?

[NikolaMilosavljevic]

@mthalman - this appears to be showing the same CI failure symptoms that #15495 addressed. Any ideas?

Could this be related to new flow from runtime that brought dependency on 4.6.0 Roslyn compiler? Due to repo re-ordering, we are now using Roslyn compiler that is in SDK:
https://github.com/dotnet/runtime/blob/a9dcf995cca0c5085c4e9bfacc43394d20569f68/eng/Versions.props#L27-L28

This creates the following warnings that later cause errors:

2023-02-17T16:32:45.4492089Z     CSC : warning CS8784: Generator 'JSExportGenerator' failed to initialize. It will not contribute to the output and compilation errors may occur as a result. Exception was of type 'FileNotFoundException' with message 'Could not load file or assembly 'Microsoft.CodeAnalysis, Version=4.6.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. The system cannot find the file specified. [/vmr/src/runtime/artifacts/source-build/self/src/src/tasks/AndroidAppBuilder/AndroidAppBuilder.csproj]

[MichaelSimons]

Could this be related to new flow from runtime that brought dependency on 4.6.0 Roslyn compiler?

IDK - I am trying to update the SDK to align with the artifacts. It is definitely strange that this appears to have the same symptoms as we say with the issue that prompted #15495.

[MichaelSimons]

It dawned on me that updating the SDK and artifacts now is not the correct action. This is going to happen as part of the preview 1 release. I reverted the changes. We will likely encounter the issue surfaced here later on.