Makefile consilidation to improve maintenance and developer experience

[chrischdi]

User Story

As a maintainer I would like to have as less Makefiles as possible for reducing the effort of syncing changes in-between different Makefiles.

As a developer I would like to use make help for getting an overview about all make targets.

Detailed Description

The file test/infrastructure/docker/Makefile contains lots of duplicate target entries which are equivalent or similar to the ones in Makefile.
Lot's of PRs require equivalent changes for Makefile and test/infrastructure/docker/Makefile:

• 🌱 Upgrade to Go 1.17, controller-runtime v0.11.x, k8s.io v1.23.0-alpha.4 #5633
• 🌱 Install hack/tools with temporary go module #5741
• 🌱 make Cluster API dev tooling to work on arm64 #5547

Some changes may not get replicated to the nested Makefile

• split of generate targets in ⚠️ Prepare for v1beta1 #5248

[A clear and concise description of what you want to happen.]

Anything else you would like to add:

[Miscellaneous information that will assist in solving the issue.]

/kind feature

[chrischdi]

/area cleanup

[k8s-ci-robot]

@chrischdi: The label(s) area/cleanup cannot be applied, because the repository doesn't have them.

In response to this:

/area cleanup

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[chrischdi]

/kind cleanup

[sbueringer]

Absolutely +1 from my side :)

[fabriziopandini]

/assign @chrischdi
given that there is already a PR for this