Disable 'rancher-kubeconfigs' feature gate in charts

[furkatgofurov7]

What this PR does / why we need it:
'rancher-kubeconfigs' FG introduced in #178 was meant to test CAPI >=v1.5.x in turtles at the time Rancher was not ready yet. However, with the newer Rancher version (v2.9.x using CAPI v1.7.x) it should be possible to test newer version of CAPI without this feature gate enabled. Moreover, update-labels test suite this FG by explicitly setting it to true anyways, but by default we should not expose it as enabled in charts.

Additionally, it is a follow-up to #658 to bump leftover dependencies to newer versions.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Checklist:

• squashed commits into logical changes
• includes documentation
• adds unit tests
• adds or updates e2e tests

[Danil-Grigorev]

@furkatgofurov7 After thinking about I’m under the impression we need to do the opposite of what this PR suggests. Always apply label on the secrets, and never disable it.

Unless there is a confidence that existing rancher code performs this task instead of turtles already. If you have a link, then it lgtm

[furkatgofurov7]

@furkatgofurov7 After thinking about I’m under the impression we need to do the opposite of what this PR suggests. Always apply label on the secrets, and never disable it.

Unless there is a confidence that existing rancher code performs this task instead of turtles already. If you have a link, then it lgtm

@Danil-Grigorev here you go:

• Turtles FG was introduced and merged in 11/2023: feat: add v2prov kubeconfig label patching #178
• Rancher issue: [RFE] Add labels to CAPI kubeconfig secrets rancher#42333
• Rancher 2.9 PR merged in 1/2024: [v2.9] feat: added capi label to kubeconfig secrets rancher#43897

[furkatgofurov7]

@alexander-demicev what are your thoughts on this, do you foresee any problems with disabling this FG by default?

[alexander-demicev]

@furkatgofurov7 It should be fine to disable it