Update dependency ray to v2.6.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
ray	>=2.6.2 -> >=2.6.3

---

Release Notes

ray-project/ray (ray)

v2.6.3

Compare Source

The Ray 2.6.3 patch release contains fixes for Ray Serve, and Ray Core streaming generators.

Ray Core

🔨 Fixes:

• [Core][Streaming Generator] Fix memory leak from the end of object stream object #​38152 (#​38206)

Ray Serve

🔨 Fixes:

• [Serve] Fix serve run help message (#​37859) (#​38018)
• [Serve] Decrement ray_serve_deployment_queued_queries when client disconnects (#​37965) (#​38020)

RLib

📖 Documentation:

• [RLlib][docs] Learner API Docs (#​37729) (#​38137)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[akihikokuroda]

LGTM on m1 Mac.

[psschwei]

hmmm... one thing I just noticed is that the ray image uses v2.5.0:

https://github.com/Qiskit-Extensions/quantum-serverless/blob/a4a6bd51a08353a18886558080f7077d9da304f0/Dockerfile-ray-node#L3

But since we aren't using the requirements.txt file in the docker build, I don't think that change is getting picked up... we probably want to standardize on using requirements to set dependencies (or whatever #901 lands on)

[psschwei]

I think it's probably ok to merge this (the tests passed, so the client build should be fine) and then standardize on how we set dependency versions as part of #901

[psschwei]

But since we aren't using the requirements.txt file in the docker build, I don't think that change is getting picked up... we probably want to standardize on using requirements to set dependencies (or whatever #901 lands on)

Just checked, and I was wrong -- the notebook / ray images do have ray v2.6.3 ... still probably should update the dockerfile, but maybe the bot will do that after this merges...