[Decouple] Make the build process the same for dev and production

[wbeckler]

Describe the bug

There is a discrepancy in resolved imports when running yarn start via any yarn build* command - e.g., yarn build-platform.

Specifically, some imports resolve successfully when running a compiled cluster via yarn build, but for some reason not resolve and show as undefined when running a cluster with yarn start

See #4333

I have added the "Decouple" tag because the strengthening of our CI that we need to increase confidence in cross-version setups will also require confidence that we're always building, testing and running the same thing.

The proposal for this issue is to simply remove the two different build tracks, so that there is one build process for dev and release.

[wbeckler]

Here the issue is at root about the gap between what's available in jenkins vs local builds