Bring back Random.Shared API once new SDK is picked up

[HaoK]

Noticed this while looking at why the blazor template tests are 100% failing now in the quarantined runs:

Related to this PR: https://github.com/dotnet/aspnetcore/pull/31453/files

https://dev.azure.com/dnceng/public/_test/analytics?definitionId=869&contextType=build

C:\h\w\BABC09DD\w\A5850946\e\Templates\BaseFolder\AspNet.klo4c0qemnm\Server\Controllers\WeatherForecastController.cs(35,39): error CS0117: 'Random' does not contain a definition for 'Shared' [C:\h\w\BABC09DD\w\A5850946\e\Templates\BaseFolder\AspNet.klo4c0qemnm\Server\AspNet.klo4c0qemnm.Server.csproj]
C:\h\w\BABC09DD\w\A5850946\e\Templates\BaseFolder\AspNet.klo4c0qemnm\Server\Controllers\WeatherForecastController.cs(36,44): error CS0117: 'Random' does not contain a definition for 'Shared' [C:\h\w\BABC09DD\w\A5850946\e\Templates\BaseFolder\AspNet.klo4c0qemnm\Server\AspNet.klo4c0qemnm.Server.csproj]

[javiercn]

@HaoK good catch.

I ran into this last week too, I thought it was because we were missing an updated SDK on the repo. I expect these to go away once we update the SDK in our repo

[davidfowl]

When will that happen?

[javiercn]

@davidfowl My understanding is before we ship preview4, otherwise we need to back this change out on Friday.

[davidfowl]

Are the tests being skipped? Do we know when the update is coming? In general we shouldn't merge these until the dependency PR flows in.

[javiercn]

@davidfowl agree.

This was originally a community contribution. We rely on CTI tests for the SPA templates and the Blazor tests are quarantined at the moment while we work on improving their reliability

[javiercn]

@davidfowl here is a PR to revert the commit #31795

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. Because it's not immediately obvious that this is a bug in our framework, we would like to keep this around to collect more feedback, which can later help us determine the impact of it. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.