[WIP] Add support for Ray 2.8.1

[arnavgarg1]

Code Pull Requests

Please provide the following:

• a clear explanation of what your code does
• if applicable, a reference to an issue
• a reproducible test for your PR (code, config and data sample)

Documentation Pull Requests

Note that the documentation HTML files are in docs/ while the Markdown sources are in mkdocs/docs.

If you are proposing a modification to the documentation you should change only the Markdown files.

api.md is automatically generated from the docstrings in the code, so if you want to change something in that file, first modify ludwig/api.py docstring, then run mkdocs/code_docs_autogen.py, which will create mkdocs/docs/api.md .

[github-actions]

Unit Test Results

  6 files  ±0    6 suites  ±0   13m 59s ⏱️ -4s
12 tests ±0    9 ✔️ ±0    3 💤 ±0  0 ❌ ±0 
60 runs  ±0  42 ✔️ ±0  18 💤 ±0  0 ❌ ±0 

Results for commit 72e47f4. ± Comparison against base commit 7e34450.

♻️ This comment has been updated with latest results.

[mhabedank]

Hi @arnavgarg1 I am cleaning the repo. We have the impression that it is quite important to update ray to newer version - there were a lot of problems in the past. Is this PR still helpful or do we need to redo the work because all this here is outdated?

Thanks for your help :-)