Add new rancher setting patch in e2e

[alexander-demicev]

What this PR does / why we need it:

For testing purposes we need to set agent-tls-mode to system-store. More details on the setting here: rancher/rancher#45684

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

[furkatgofurov7]

@alexander-demicev I checked new setting was introduced in rancher-2.9? And we recently bumped it in turtles e2e #658. Should we re-trigger e2e tests once again to test it?

[alexander-demicev]

@furkatgofurov7 I rebased the PR

[furkatgofurov7]

Deferring on CI, but this looks good

[Danil-Grigorev]

Can you elaborate more why is this setting needed?

[furkatgofurov7]

Can you elaborate more why is this setting needed?

@Danil-Grigorev rancher/rancher#45628 (comment) should give an idea

[Danil-Grigorev]

@furkatgofurov7 but this does not explain why we test this setting in our suite, does rancher missing this coverage? Since this has to be enabled with turtles on helm chart installation also to be effective for real import scenarios outside of e2e

[alexander-demicev]

@Danil-Grigorev Defaulting to "strict" is a breaking change for anyone using ngrok in the way we're used to, when enabled allows only certificates verified with CAcerts authority provided by cacerts rancher setting will be used.
This is something that Rancher users have to configure on their own and shouldn't be related to how turtles import clusters. I believe that by using system-store we are not testing new functionality and using the setup we had before.
Here are a couple links to related PRs:
rancher/fleet#2507
rancher/rancher#45909

I'm not against extending the E2E suite to use "strict" mode for all our suites but it can done later separately.

[Danil-Grigorev]

I'm confused @alexander-demicev as I was not advocating for using strict mode, see #660 (comment)

So if you saying that strict became new default, and by applying it we re-enables use of ngrok, change makes sense to me.

(Maybe this needs to be mentioned in PR description?)

[alexander-demicev]

@Danil-Grigorev We will need to provide CA public key for ngrok(or anything else) if using strict, which shouldn't be a problem for us or users but it can be addressed separately