Test CAPI upgrade when installing from `ConfigMap`

[salasberryfin]

Description

Core CAPI is now installed from embedded ConfigMap, and there's no remote fetch unless the user explicitly configures the chart with a remote URL. Turtles creates a single ConfigMap resource that contains the manifest and a pre-configured matchLabels selector is used to filter the correct ConfigMap. However, as a user I may want to create multiple ConfigMap with different versions of core CAPI and we need to verify that this configuration does not break the installation process.

Definition of Done

At least two new tests should be added that cover this setting:

1. Going from Turtles vx.x.1 with core CAPI vx.x.1 -> to Turtles vx.x.2 with core CAPI vx.x.2: during upgrade, the controller should automatically move from the older version of core CAPI to the new one. The ConfigMap should contain the manifest with the most recent version of CAPI and the selector should match the correct resource. If two ConfigMap that satisfy the matchLabels exist, it should pick the latest version.
2. While on Turtles vx.x.1, if user creates a new ConfigMap that matches the selector, it should not break the installation of core CAPI.