Vendor envtest and other tooling across Cluster Infra team repo

User Story

As a developer i want to have my testing and build tooling managed in a consistent way for reduce amount of context switches during doing a maintenance work. 

Background

Currently our approach to manage and update auxiliary tooling (such as envtest, controller-gen, etc) is inconsistent. Fine pattern was introduced in CPMS repo, which relies on golang toolchain for update, vendor and run this auxiliary tooling.

For CPMS context see: 

https://github.com/openshift/cluster-control-plane-machine-set-operator/blob/main/tools/tools.go

https://github.com/openshift/cluster-control-plane-machine-set-operator/blob/main/go.mod#L24

https://github.com/openshift/cluster-control-plane-machine-set-operator/blob/main/Makefile#L19

Steps

• Align envtest, controller-gen and other tooling management with pattern introduced within CPMS repo
• Introduce additional test which compares envtest version (if envtest is in use within particular repo) with using k8s related libraries version. This will help to not forget to update envtest and other aux tools during dependency bumps.

Stakeholders

• Cluster infra team

Definition of Done

• All Cluster Infra Team owned repos updated and uses consistent pattern for auxiliary tools management

• • REPO LIST TBD, raw below
  • MAPI providers
  • MAO
  • CCCMO
  • CMA

• Testing

• Existing tests should pass
• additional test for checking envtest version should be introduced