Use ray-project fork in CI build and Dockerfile

[glennmoy]

Uses our upstream branch of the ray project instead of our forked repo in the CI and docker file

[glennmoy]

A bit of wrinkle in getting this to work is that the ray args can longer be parsed from raylet.out as the full commandisn't reported there anymore. We might be able to still parse some args from raylet.out or elsewhere but it might also be better to revisit #52

[glennmoy]

Current issue is that newer versions of RAy ship with the autogenereated protobuf files checked in as of ray-project/ray#39210, and rebuilding ray from source doesn't seem to regenerate them.

Thus it isn't picking up on the Language::JULIA support that we added to the source files.
As a resuilt it cannot spawn worker processes and the task.jl tests fail.