Update docs for kube_config generation when kubeconfig-generate-token=false

Author: rawmind0

docs/resources/cluster.md

@@ -620,6 +620,8 @@ The following attributes are exported:
 * `ca_cert` - (Computed/Sensitive) K8s cluster ca cert (string)
 * `system_project_id` - (Computed) System project ID for the cluster (string)
 
+**Note** For Rancher 2.6.0 and above: if setting `kubeconfig-generate-token=false` then the generated `kube_config` will not contain any user token. `kubectl` will generate the user token executing the [rancher cli](https://github.com/rancher/cli/releases/tag/v2.6.0), so it should be installed previously.
+
 ## Nested blocks
 
 ### `agent_env_vars`

docs/resources/cluster_sync.md

@@ -103,6 +103,8 @@ The following attributes are exported:
 * `nodes` - (Computed) The cluster nodes (list).
 * `system_project_id` - (Computed) System project ID for the cluster sync (string)
 
+**Note** For Rancher 2.6.0 and above: if setting `kubeconfig-generate-token=false` then the generated `kube_config` will not contain any user token. `kubectl` will generate the user token executing the [rancher cli](https://github.com/rancher/cli/releases/tag/v2.6.0), so it should be installed previously.
+
 ## Nested blocks
 
 ### `nodes`

docs/resources/cluster_v2.md

@@ -234,6 +234,8 @@ The following attributes are exported:
 * `cluster_v1_id` - (Computed) Cluster v1 id for cluster v2. (e.g to be used with `rancher2_sync`) (string)
 * `resource_version` - (Computed) Cluster v2 k8s resource version (string)
 
+**Note** For Rancher 2.6.0 and above: if setting `kubeconfig-generate-token=false` then the generated `kube_config` will not contain any user token. `kubectl` will generate the user token executing the [rancher cli](https://github.com/rancher/cli/releases/tag/v2.6.0), so it should be installed previously.
+
 ## Nested blocks
 
 ### `agent_env_vars`