transparently use docker targets when building

[jaxesn]

Issue #, if available:

Description of changes:

We have traditionally relied on building our components on the host, which requires a fair amount of setup and dependencies. A while back we did introduce the run-in-docker target(s) to make it easier to run parts of the build locally and match checksums/attribution files by using a docker container running the builder-base image which is what we run in prow/coudebuild. Recently we started using EKS-D golang builds which are only produced for linux so building on mac and matching checksums (which was possible before) is no longer possible. Using the builder-base docker approach has worked pretty well.

This PR extends our use of these docker container by converting certain targets, go build/go licenses/attribution and some project specific targets, to use docker automatically if the required toolset is missing. In the case of golang, we just assume its missing since the likelihood of someone having install EKS-D go is not very high. This can be overridden if the developer wants to build on the host instead of the container.

The approach used in Common.mk to run the docker targets transparently is a bit hacky.... Its basically the same approach documented and taken in #2546. The good new is that for project Makefiles where we want to use docker if, say npm is missing in the case of the prometheus build, its a pretty simple change.

I did go through and update the building-locally doc, in which I created and recreated AL2 and AL23 instances to confirm I had as much documented as I could find.

I did add a build-all target to the root Makefile, which I do not intend to be used anywhere but it is a nice helper when trying to validate that an instance has all the dependencies needed to build pretty much the entire stack.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[eks-distro-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[jaxesn]

/hold

[abhay-krishna]

/lgtm
/approve

[eks-distro-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhay-krishna

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [abhay-krishna]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jaxesn]

/test all

[jaxesn]

/unhold