Update RayTaskRunner for compatibility with new engine

[desertaxle]

Updates the RayTaskRunner to be compatible with the new engine. I also moved the .map logic on the TaskRunner subclasses to the base class since it was the same between all three TaskRunner implementations.

I wanted to create a lower-level utility for running tasks with Ray's @ray.remote decorator, but Ray only allows functions and classes to be decorated with @ray.remote,, and I was having trouble smuggling a task_run_id on the returned ObjectRef. I think there's still lower-level utility hiding in there, but I figured I'd work backward from a working task runner.

Example

Checklist

• This pull request references any related issue by including "closes <link to issue>"
  • If no issue exists and your change is not a small fix, please create an issue first.
• If this pull request adds new functionality, it includes unit tests that cover the changes
• This pull request includes a label categorizing the change e.g. maintenance, fix, feature, enhancement, docs.

For documentation changes:

• This pull request includes redirect settings in netlify.toml for files that are removed or renamed.

For new functions or classes in the Python SDK:

• This pull request includes helpful docstrings.
• If a new Python file was added, this pull request contains a stub page in the Python SDK docs and an entry in mkdocs.yml navigation.

[desertaxle]

I also renamed this client to be more consistent with the DaskTaskRunner and PrefectDaskFuture.