update workspace templates base image

[sofianhnaide]

Why are these changes needed?

Update the workspace template base image to use the official Ray 2.4 release.

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 :(

[justinvyu]

Where do I find the build_id? Is it on dockerhub?

[justinvyu]

Also, can we use the byod since it has the latest alias?

#   docker_image: anyscale/ray-ml:latest-py39-gpu
#   ray_version: latest

[justinvyu]

Update from discussion with Sofian:

• Product does not support "anonymous" cluster envs. So, if we do a BYOD solution, then every new template they create will show up as a new cluster env in their cluster envs listing page.
• So, we'll start with base images build ids.
• The product code-path already supports BYOD, so it would be easy to transition.

[sofianhnaide]

Where do I find the build_id? Is it on dockerhub?

I believe all the config are under "backend/config" in the product repo and they map into docker hub. They do follow the same convention and I included examples for nightly and release versions.