Re-introduce the ProvisionerClass API

[timflannagan]

Goal: implement the ProvisionerClass API and update any controllers so there's a layer of indirection between Bundles and BundleDeployments, and enables parameterization of provisioners.

In preparation of migrating the kuberpak provisioner to this repository, we removed the out-of-date ProvisionerClass API in #40.

AC:

• Introduce a provisionerclass_types.go to api/v1alpha1
• Ensure a ProvisionerClass CRD is generated in the root manifests/ directory
• Update the Bundle and BundleDeployment type definitions to reference the metadat.Name of an existing ProvisionerClass (vs. the unique provisioner ID like it's currently referencing)
• Update any provisioner implementations (e.g. k8s, registry+v1, etc.) and make the requisite API breaking changes

Stretch goal:

• Filter out Bundles and BundleDeployments that don't match the metadata.Name of a ProvisionerClass that references that unique provisioner ID
• Add support for configuring provisioners based on the parameters listed in a ProvisionerClass resource

[github-actions[bot]]

This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.