Revert "Revert "Improve components infrastructure (#12145)" (#12679)"

[JunTaoLuo]

This reverts commit e2d57e2.

As per meeting discussion, this is the approach we would like to take for source build as well. However, there will likely be pieces of the infrastructure that needs to be modified (e.g. not redistributing yarn binaries) but we'll address those separately.

I'm adding the original changes to preview 9 for improving workflow.

[dougbu]

Has anything changed in this since the original PR? If yes, where should we dive deeper?

[rynowak]

revert revert is the best kind of revert. Prove me wrong.

[JunTaoLuo]

I'm going to update with a few more details on how I intend for this to work when all tests come back clean but I believe this is close to ready.

[dougbu]

Still looks good.

[JunTaoLuo]

Here's a few of the common scenarios and how it will work when you run build by default (i.e. without specifying BuildNodeJs or NoBuildNodeJS):

Scenario	node installed	no node
build.cmd in root	builds dependent npm projects	uses checked in assets if available, displays warning
build.cmd in src/Components	builds dependent npm projects	uses checked in assets if available, displays warning
dotnet build on Microsoft.AspNetCore.Components.Server	builds dependent npm projects	uses checked in assets if available, displays warning
yarn run build on Web.JS npmproj	does not build dependent projects	fails

With explicit specification of BuildNodeJs:
The dependent npm projects will be built if node is available on the path and the build will fail if it's not.

With explicit specification of NoBuildNodeJs:
The dependent npm projects will not be built and the JS artifacts from previous builds will be used. If the JS artifacts are not present (only the release versions are checked into source control) the build will fail

[halter73]

@rynowak, @pranavkm calls your revert revert and raises to revert revert revert.

[rynowak]

Dank.

[JunTaoLuo]

Revertception