Ray API Organization

[tovacinni]

Right now, most of our ray-based features in the internal MR are located in ops.spc or render.spc. As we move beyond SPC and support general ray-based pipelines, we should have a place to package these.

Candidates might be ops.ray and / or render.ray. I'm not super clear on how we should make the decision of for which to include each function.