Problem:
We used to just log error when failed to deploy/withdraw systemMonitor, if it failed to deploy prometheus-operator, no error return cause operator isn't get deployed until next time cluster sync.

Solution:
Return error when failed to deploy/withdraw systemMonitor

Issue:
https://github.com/rancher/rancher/issues/29318

Fix deploy agents

A mistake was made in the code for clusters with private API endpoint
that caused the cluster/node agents to not be deployed.

[v2.5] vendor update rke

[2.5] Revert "Remove basic auth for GKE"

[2.5] Allow communication with EKS clusters with private API endpoint

Rancher is able to import and create clusters with private API endpoint,
but is not able to communicate with them afterwards. Now, as long as the
agent is deployed, rancher is able to tunnel to communicate with the
API.

[2.5] Bump go version to 1.14.12

This reverts commit 1a3e7780.

The tokens being used expire after 1 hour and are not being refreshed. A
mechanism for token refresh should be implemented.

[2.5]Fix windows cluster not being detected

[2.5] Backport: Add fleetworkspace admin, member and readonly roles

[v2.5] [netpol] don't add back hostport labels for pods of system ns

This commit introduces changes to try harder to prevent the following error from appearing:
```
2020/11/25 15:53:58 [ERROR] API error response 500 for POST /v3/clusters/c-l4bdt?action=enableMonitoring. Cause: Operation cannot be fulfilled on clusters.management.cattle.io "c-l4bdt": the object has been modified; please apply your changes to the latest version and try again
```

The root cause of this error is that we do not normally retry on a conflict, so before it was appearing even after spinning up just 4 clusters in succession and trying to immediately enable monitoring.

Related Issue: https://github.com/rancher/rancher/issues/30188

Signed-off-by: Arvind Iyengar <arvind.iyengar@rancher.com>
(cherry picked from commit fa66cced)

[release/v2.5] Aci cni backport

Add support for startTLS

Signed-off-by: Kiran Shastri <shastrinator@gmail.com>
(cherry picked from commit 0af5ba82)

Signed-off-by: Kiran Shastri <shastrinator@gmail.com>

Signed-off-by: Kiran Shastri <shastrinator@gmail.com>

[2.5] Updated chart and tests to allow specify ember and vue Rancher custom logos persistence

[v2.5] add mirantis check + typos/grammar

[2.5]Backport-Add ability to set password for rancherd

[2.5] Update provider detector to include rke.windows

Adds options to global DNS [2.5]

[2.5] Backport: Update rancherd to point to rke2 v1.18.12+rke2r1

Problem:
We removed podname label for hostport pods of system ns, but
doesn't return from there resulting into adding back the labels again.

[forwardport] Move creation of accesscontrol

Problem:
When a cluster agent is diconnected rancher tries to start the
controllers in a slow loop, but this causes a memory leak. The leak
stems from adding a handler in client-go which has no method to
deregister the handler so a fixed size array leaks every time.

Solution:
Don't create access control until Rancher has verified a connection to
the cluster which is a good indication controllers will start. There is
technically a small leak here every time we start these controllers.

[2.5] Backport http proxy fleet