disable ray tests for latest torch release

[winglian]

Description

Disabling ray tests on latest torch 2.6.0 for now. Per @erictang000

it looks like the issue is actually with triton 3.2.0 and ray.
Bug details:
deepspeed uses the @triton.autotuner decorator, which gets initialized at import time in triton 3.2.0,
they add logic to the autotuner that checks torch.cuda.is_available() in the autotuner constructor
the ray TrainTrainable cpu only actor, which packages environments for the RayTrainWorker gpu actors, 
tries to import deepspeed but torch.cuda.is_available() is false, and the new triton version doesn't like that

Fixing triton to 3.1.0 will fix the issue for now, but this might cause other issues with torch 2.6.0 since triton==3.2.0 
was a dependency. We're looking into the best way to resolve this either on our end or through putting an issue up 
on deepspeed to allow a way to avoid the offending triton autotuner code.