Co-authored-by: shalin patel <[email protected]>

Upstream stopped building the executable in a container. We continue to
build it in a container, so that we can have multi-arch images.

A recent PR[1] updated the godoc comment that describes the
VCDMachineSpec MachineAddress field, but the change was not reflected in
the v1beta1 CRD.

This updates the comment in the CRD base, as well as
infrastructure-components.yaml

[1]: vmware#445

make runs each line in a separate shell. In a recent commit[1], commands
on one line were split to multiple lines. When `go test` ran, it did not
have the environment variable required by envtest, and failed.

[1]: https://github.com/vmware/cluster-api-provider-cloud-director/pull/466/files#diff-76ed074a9305c04054cdebb9e9aad2d818052b07091de1f20cad0bbac34ffb52R129-R134

A recent PR[1] introduced the use of a relative path for envtest assets.
The path is relative to the repository root, and this means Go tests,
which run relative to their package path, cannot find the envtest
assets, and fail.

[1]: https://github.com/vmware/cluster-api-provider-cloud-director/pull/466/files#diff-76ed074a9305c04054cdebb9e9aad2d818052b07091de1f20cad0bbac34ffb52R129-R134

It is sometimes necessary to skip some tests. For example, to skip the
e2e tests, run:

```shell
make test TEST_PACKAGES='$(shell go list ./... | grep -v 'tests/e2e')'
```