Add support for upgrading eks-anywhere components

[jaxesn]

Currently the upgrade command can only upgrade Kubernetes versions. We need to support updating the eks-anywhere components, including capi/capv.

Until we can support this, we may need to introduce a new release mode to support generating new release bundles with only Kubernetes (eks-distro) updates included so customers can update to new Kubernetes versions.

---

Design doc

In order to be able to gain some upgrade capabilities as soon as possible (due to the dependency of other features on this one), we split the work on 3 chunks. These could be moved to separate issues if necessary (for example if we decide to release the first or first a second ones in an early release):

Minimal functionality

This provides upgrades for all components except for Cilium and any CAPI version bump that involves an API version change. It doesn't include E2E tests and any Bundle/patch cli version would involve significant manual work and testing. It is preferred, if possible, to release this together with, the second set of tasks.

• Dependency factory #310
• Feature flag package #311
• Versions with build metadata in bundles manifest for all components #312
• Get currently installed VersionsBundle #313
• CAPI upgrades #314
• EKS-A and CRDs upgrade #315
• Flux upgrades #316
• Revisit "upgrade needed" logic #399
• Upgrade components during upgrade cluster command #317
• Add extra checks to component upgrades for management clusters #463
• Update/create new bundle object in the cluster #458
• Docs for "upgrading to the latest version of components" #318
• Docs for new upgrade cluster command's behavior #319

Automation

This provides proper automated testing and reduces to a minimum the amount of manual work for new Bundle releases.

Moved to #551

Full feature

Moved to #551

[mitalipaygude]

Closing this issue out; the automation testing and the full features have been added to #551