Rancher provisioned/managed RKE2/K3s data-dir support

There is currently an ongoing effort to support specifying the RKE2/K3s data-dir argument, which allows a user to change it from the default of /var/lib/rancher/rke2 & /var/lib/rancher/k3s respectively, to a user provided directory. I've found the following instances of these directories hardcoded within the project:

• https://github.com/rancher/support-bundle-kit/blob/5f66ca8d79fcfc098480d34c437a7bfb035ac729/hack/collector-longhorn#L7
• https://github.com/rancher/support-bundle-kit/blob/5f66ca8d79fcfc098480d34c437a7bfb035ac729/hack/collector-harvester#L48
• https://github.com/rancher/support-bundle-kit/blob/5f66ca8d79fcfc098480d34c437a7bfb035ac729/hack/collector-harvester#L111-L112

Please review the above information, and feel free to reach out to me regarding questions. The api changes can be found within this draft PR within rancher/rancher: https://github.com/rancher/rancher/pull/45326/files#diff-6f7b3ace8ec7df668da64642416a1171322908df345c8e339d314bac3ed08af6R57.

Start by reading hack/collector-longhorn and hack/collector-harvester, especially the lines linked in the issue, and compare their hardcoded RKE2/K3s data directories with the API changes referenced in the Rancher draft PR. Done means the affected collectors support user-provided data directories rather than assuming the defaults; check the repository's existing validation afterward.