[backport v2.10.7] Preserve valid user-supplied chart values in rke2 form

[github-actions]

This is an automated request to port PR #14261 by @rak-phillip

fixes #14074

Original PR body:

Summary

This adds a wider range of valid charts to be applied to user-supplied chart values; these additional charts will prevent these values from being removed from user-supplied yaml if they match.

Fixes #12002

Occurred changes and/or fixed issues

• Add additional rke2 charts to the collection of accepted chart values in rkeconfig

Technical notes summary

The initial implementation of applyChartValues() only takes into account addons, but that doesn't appear to be the correct approach for this method because there's a wider range of potential valid charts available.

I don't think that it makes sense for the form to pave over user values without notifying them of such a change - this is the root cause of the issue. A better approach would be to parse the user-supplied charts and notify the user of any potential issues, leaving the responsibility the the user to resolve any problems. Ultimately, making such a change in behavior is outside of the scope of this issue, but I think patterns like these can be helpful in future development.

Areas or cases that should be tested

The associated issue has sufficient reproduction steps.

Areas which could experience regressions

This is purely additive. This could cause problems if any of these rke2 charts are not intended to be in the rkeconfig charts.

Screenshot/Video

NA

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes