[release-v2.11] Move helm charts from rancher/charts to /charts dir

[pratikjagrut]

PR Description

We're integrating the Auto Chart Bumps feature into the System Upgrade Controller (SUC) repository to streamline chart maintenance and align with Rancher's release structure.

Why This Change?

• Currently, the SUC chart resides in rancher/charts, but due to strict requirements, we need a separate repo for managing SUC chart.
• One key requirement is maintaining three active release branches for Rancher, which makes it difficult to continue hosting the chart in the rancher/charts repository.
• Instead of creating a new repository, we've decided to host the SUC chart in a dedicated branch within the existing SUC repo.
• We'll use the same branch for all three active releases instead of three branches.

What’s Changing?

• A new branch, rancher-charts-release/v2.11, will be used exclusively for SUC charts.
• All new PRs for the Rancher SUC chart will be created in this branch instead of rancher/charts.
• This branch will only contain the SUC chart files, not the SUC source code.
• The auto chart bump mechanism will automatically watch this branch and update charts.

Related issue: #49087.

[snasovich]

There is now https://github.com/rancher/charts/tree/dev-v2.11/charts/system-upgrade-controller/106.0.0 for v2.11.0 so we should use it as the base.

[pratikjagrut]

There is now https://github.com/rancher/charts/tree/dev-v2.11/charts/system-upgrade-controller/106.0.0 for v2.11.0 so we should use it as the base.

@snasovich Done.

[jiaqiluo]

Changes look good to me, they are identical to the chart at https://github.com/rancher/charts/tree/dev-v2.11/charts/system-upgrade-controller/106.0.0

Hi @pratikjagrut, is it true that, instead of maintaining the (most-of-the-time-idential) templates in multiple branches in the rancher/charts repo, we will maintain them in multiple branches here? So, if we need to add a change to the chart and release a new version of the chart in both Rancher 2.10 and 2.11 release lines, we will need to raise 2 PRs in this repo to the corresponding branches, is it right?

[pratikjagrut]

@jiaqiluo Yes, that is correct.