Helm: add support for auto upgrading CRDs

[benashz]

Introduces a pre-upgrade hook that will upgrade/create any of the CRD manifests that are bundled in the vso docker image.

Other fixes:

• make the component label test more reliable by checking all documents individually.
• configure a backoff in the pre-delete "pdcc" Job.

Overview of the approach:

• Extend VSO to support upgrading the CRDs directly
• Include the CRD manifests in the VSO image
• Extend the Helm chart to deploy a pre-upgrade hook that invokes the upgrade process

Out of scope:

• support for rollback/downgrades.
• removal of obsolete CRDs

Update to the Helm values:

# Configure the behaviour of Helm hooks.
hooks:
  # Resources common to all hooks.
  resources:
    limits:
      cpu: 500m
      memory: 128Mi
    requests:
      cpu: 10m
      memory: 64Mi
  # Configure the Helm pre-upgrade hook that handles custom resource definition (CRD) upgrades.
  upgradeCRDs:
    # Set to true to automatically upgrade the CRDs.
    # Disabling this will require manual intervention to upgrade the CRDs, so it is recommended to
    # always leave it enabled.
    # @type: boolean
    enabled: true

    # Limit the number of retries for the CRD upgrade.
    # @type: integer
    backoffLimit:  5

    # Set the timeout for the CRD upgrade. The operation should typically take less than 5s
    # to complete.
    # @type: string
    executionTimeout: 30s

[tvoran]

Left a few minor questions, and I'm wondering if we need to check the Status block on upgrades, but on the whole 👍