Report virtual cluster version on mirrored nodes

With mirrorHostNodes enabled the node object copies the host node's
status wholesale, including NodeInfo.KubeletVersion — so a virtual
cluster on a newer Kubernetes than its host advertises the host's older
version, misleading version-gated consumers. Keep the virtual cluster's
version, as the non-mirrored path already does.

v1.2.0-rc3-ivx3: ivx2 + node syncer for mirrorHostNodes (live cordon/…

…taint/label propagation)

v1.2.0-rc3-ivx2: ivx1 + mirrored-node version fix (report vc version,…

… not host version)

v1.2.0-rc3-ivx1: upstream main (bd8ed8a, post-rc3 incl. rancher#1128 …

…SA-token fix, rancher#1117 reset-crash fix) + LB-status/ipFamily sync patch (rancher#1104)

Skip expensive CI for Markdown-only PRs (rancher#1052)

* ci: skip expensive checks for markdown-only PRs

Signed-off-by: nightcityblade <nightcityblade@gmail.com>

* ci: skip docs directory in expensive checks

---------

Signed-off-by: nightcityblade <nightcityblade@gmail.com>
Co-authored-by: nightcityblade <nightcityblade@gmail.com>

Bump charts to `v1.2.0-rc1` (rancher#1096)

Update GitHub Actions (rancher#1039)

Co-authored-by: renovate-rancher[bot] <119870437+renovate-rancher[bot]@users.noreply.github.com>

Bump charts to `v1.2.0-rc1` (rancher#1043)

Bump charts to `1.1.0` (rancher#851)

Bump charts to `1.0.3` (rancher#850)