Changing token / agent-token required for security restart log needs update

[ShylajaDevadiga]

Environmental Info:
RKE2 Version:
Commit: 45c2122

Node(s) CPU architecture, OS, and Version:
Ubuntu 22.04

Cluster Configuration:
Single or multi node

Describe the bug:
Log message on the console output need to be updated to restart rke2 instead of restart k3s

$ rke2 token rotate --token token1 --new-token=token2
WARNING: Recommended to keep a record of the old token. If restoring from a snapshot, you must use the token associated with that snapshot.
WARN[0000] Cluster CA certificate is not trusted by the host CA bundle, but the token does not include a CA hash. Use the full token from the server's node-token file to enable Cluster CA validation.
Token rotated, restart k3s with new token

Steps To Reproduce:

1. Install rke2
2. run rke2 token rotate --token token1 --new-token=token2 to change the server token

Expected behavior:
Token rotated, restart rke2 with new token

Actual behavior:
Token rotated, restart k3s with new token

Additional context / logs:

[dereknola]

/backport v1.25.15+rke2r1 v1.26.10+rke2r1 v1.27.7+rke2r1

[ShylajaDevadiga]

Validated on rke2 version v1.28.3-rc2+rke2r1

Environment Details

Infrastructure
Cloud EC2 instance

Node(s) CPU architecture, OS, and Version:
Ubuntu 22.04

Cluster Configuration:
3 server 1 agent

Config.yaml:

$ cat /etc/rancher/rke2/config.yaml 
write-kubeconfig-mode: "0644"
token: token1
node-external-ip: <IP>

Steps to reproduce the issue and validate the fix

1. Copy config.yaml
2. Install rke2
3. As non-root user rke2 token rotate --token token1 --new-token=token2
4. Update config.yaml with new token
5. Restart rke2 service on all nodes
6. Reboot all nodes
7. Verify token is updated on every node, cluster is up and pods are in running state

Validated the log message on the console output displays correct distro

rke2 token rotate --token token1 --new-token=token2
WARNING: Recommended to keep a record of the old token. If restoring from a snapshot, you must use the token associated with that snapshot.
Token rotated, restart rke2 nodes with new token