[Doc][KubeRay] Improve KubeRay docs based on CUJ (part 2)

[kevin85421]

Why are these changes needed?

• I changed the KubeRay docs from v1.1.0 to v1.1.1 in [Doc][KubeRay v1.1.1] Use KubeRay v1.1.1 in KubeRay-related docs #45185. However, I didn't create a new branch for v1.1.1; instead, I used the existing release-1.1.0 branch and added a new tag for v1.1.1. The following command will report 404 when we download a YAML because release-1.1.1 branch doesn't exist.

  curl -LO https://raw.githubusercontent.com/ray-project/kuberay/release-1.1.1/ray-operator/config/samples/ray-cluster.autoscaler.yaml

  This PR updates release-1.1.1 to the tag v1.1.1.

  kubectl apply -f https://raw.githubusercontent.com/ray-project/kuberay/v1.1.1/ray-operator/config/samples/ray-cluster.autoscaler.yaml

• Use the same K8s version for all kind create commands.

• Remove "on any node of" from "Run the driver script directly on any node of the Ray cluster, for interactive development.". In most cases, users don't need to understand where to run the driver processes. In addition, the description may make users confusion with the above descriptions for Ray head node.

Related issue number

Checks

• I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
• I've run scripts/format.sh to lint the changes in this PR.
• I've included any doc changes needed for https://docs.ray.io/en/master/.
  • I've added any new APIs to the API Reference. For example, if I added a
    method in Tune, I've added it in doc/source/tune/api/ under the
    corresponding .rst file.
• I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
• Testing Strategy
  • Unit tests
  • Release tests
  • This PR is not tested :(

[aslonnie]

(not sure why this is draft?)

[kevin85421]

(not sure why this is draft?)

There is multiple feedback from CUJ. This is just part of the feedback.