Generate crd with controller gen

[181192]

About this PR

This PR enables the generation of the CRDs from the APIs, using the controller-gen cli, which is part of the KubeBuilder project.

Annotations has been added to the types to make it as close as possible as the manually created CRD.

See the diff on the generated CRD here.

Changes

Some changes was needed to be done:

• Removal of unused (?) field Poll from AzureKeyVaultObject type 2db1085
• Several annotations in the types to generate the same CRD as created manually
• Added enum's for some types 2c462e8 and f999a27
• Added AzureIdentity struct 4c44534 to align with the original CRD (this was a bug, need to make sure code references are still OK)
• Added Makefile target for generating CRD's
• Added the API for version v2alpha1 that exists in manual CRD 1cf7336 075b8fe
• Updated hack/update-codegen.sh with running code-generator inside a container and modifying repository files directly
• Populate status field as shown bellow

Previous status field was only type object with preserve unknown fields enabled

status:
  type: object
  x-kubernetes-preserve-unknown-fields: true

Now it generates with correct fields

status:
  description: AzureKeyVaultSecretStatus is the status for a AzureKeyVaultSecret resource
  properties:
    lastAzureUpdate:
      format: date-time
      type: string
    secretHash:
      type: string
    secretName:
      type: string
  required:
  - secretHash
  - secretName
  type: object

The spec field is also now required, but not status as the controller will update the status field later

schema:
  openAPIV3Schema:
    < .... > # omitted for brevity
  required:
  - spec
  type: object

Development Workflow

To generate client code

make codegen

To generate crd

make crdgen

[181192]

Missed generating clients due to having repo in non default GOPATH, updated hack/update-codegen.sh with running code-generator inside a container and modifying repository files directly.

[181192]

Introduced breaking changes with generated crd that change group and crd name, that breaks all existing azurekeyvaultsecrets.spv.no applied to a cluster.
Reverted to use group name +groupName=spv.no and added +groupGoName=AzureKeyVault to get "nicer" group names on generated Go code (Spv was a bit to general)

Added +kubebuilder:subresource:status to mark the Status field as a subresource, updating status field was failing.
Also added Age field to additional printer columns