[docs] Add gpt oss deployment example

[Aydin-ab]

Why are these changes needed?

Adding new examples for gpt-oss, later released as an anyscale templates as well

Note:

Using our latest version ray==2.49.2 + vllm 0.10.2 breaks but this seems already fixed in nightly so we can change that requirement once the next release is out (mid october)

Also, our current ray-llm image is using vllm 0.10.0 so we have to build a new image with vllm>=0.10.1 this makes the anyscale service launch pretty long (~5min)

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

[gemini-code-assist]

Code Review

This PR adds a new example for deploying gpt-oss models. The changes are mostly good, but there are a few issues. There's a critical copy-paste error in the Anyscale service configuration for gpt-oss-120b in the example notebook and README. There are also some inconsistencies in the documentation links, Docker image versions, and configuration values in the examples. The Dockerfile could also be improved for better practices. I've provided detailed comments and suggestions to address these points.

[kunling-anyscale]

.

[kunling-anyscale]

add few suggestions and comments

[Aydin-ab]

i notice the ray-llm nightly image is using vllm==0.10.2 so we can probably start the engineering review in the next release

[Aydin-ab]

i notice the ray-llm nightly image is using vllm==0.10.2 so we can probably start the engineering review in the next release

for context using our latest version ray==2.49.2 + vllm 0.10.2 breaks but this seems already fixed in nightly so we can change that requirement once the next release is out (mid october)

meanwhile we can continue and publish with this version of ray==2.49.0, vllm==0.10.1