[epic] Switch from rukpak to kapp-controller

[ncdc]

Carvel's kapp-controller does much of what rukpak does, and more.

• Add kapp-controller App spec template to FBC so operator authors can define how their content should be applied
• Create App (instead of BundleDeployment) when reconciling an Extension
• support for registry v1 bundle formats when we switch to App #608
  • convert registry v1 to plain manifests using YTT (supporting registry v1 bundles that specify use of webhooks is out of scope for now)
  • based on conversion, create app cr and apply it on cluster
• watch all namespaces #611
  • if this ends up being the same as the work outlined in [epic] Support watchNamespaces via parameterization for registry+v1 bundles in Extension API #593, can do it at the same time
• add kapp in the makefile setup #609
• remove rukpak in the makefile setup #610

[oceanc80]

Create App (instead of BundleDeployment) when reconciling an Extension - Updated

Iteration 1:

• Create App CRs with Extension controller: Create App CRs instead of BundleDeployment  #615
• Add e2e tests: (Follow up): Integrate Kapp: Add e2e tests for extension reconciler #653
• Improve resolution in extension controller: (Follow up): Integrate Kapp: Improve resolution logic in extension reconciler #654
• Improve status reporting in extension controller: (Follow up): Integrate Kapp: Improve status reporting in Extension #655
• Add support to registryV1 bundles: (Follow up): Integrate Kapp: Add support for registryV1 bundles #656
• Add kapp-controller installation to Makefile setup: add kapp in the makefile setup #609

Iteration 2:

• Remove the use of ClusterExtension
• Remove Rukpak