Use reference assemblies when compiling Razor views

[pranavkm]

Fixes #18323

[JunTaoLuo]

Please fill out the servicing template and wait for shiproom approval. We want to take this in the 3.1 patch.

[JunTaoLuo]

Changes make sense to me

[wtgodbe]

@pranavkm looks like this broke other projects, maybe have the target conditionally only run for projects that set some property (specifically the inner builds of identity.ui)?

[dougbu]

Once we get the Right Thing:tm: in this PR (perhaps, as @wtgodbe suggested, by narrowing when it's applied) should we instead take this as a tell-mode change @Pilchie❔

[pranavkm]

We verified that this also affects all the other UI projects (Azure.UI etc). I'm going to play around with this to see what's causing the build failure.

[wtgodbe]

I think this should be fine for tell mode - it's treating the same symptom as John's multi-target PR, which was approved, and that arguably could've been infra tell mode as well. @Pilchie thoughts?

[pranavkm]

This one project had an intersection of Components from the shared fx and Components as a package via Blazor. Using the ref assembly to compile here caused version mismatch during compile. This seems to be the only project that's affected by the workaround.

[Pilchie]

Let’s use tell mode for this one. I’d rather get the build unblocked ASAP.

[rynowak]

@pranavkm - do we need to port this workaround to AspNetCore-Tooling?