Handle all ray job statuses

[EngHabu]

Describe your changes

Ray operator sets a few different possible transient statuses as well as different cluster deployment statuses. The plugin doesn't handle all of them and silently attempts to make an illegal state transition instead of erroring. This change does two things:

• Update code to handle all current known statuses
• Fail hard if the job moves to an unknown status

Check all the applicable boxes

• I updated the documentation accordingly.
• All new and existing tests passed.
• All commits are signed-off.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (dd91cba) 59.10% compared to head (f4005cf) 57.97%.
Report is 2 commits behind head on master.

❗ Current head f4005cf differs from pull request most recent head 8a3ca32. Consider uploading reports for the commit 8a3ca32 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4389      +/-   ##
==========================================
- Coverage   59.10%   57.97%   -1.14%     
==========================================
  Files         614      396     -218     
  Lines       52103    29233   -22870     
==========================================
- Hits        30797    16948   -13849     
+ Misses      18853    10571    -8282     
+ Partials     2453     1714     -739     

Flag	Coverage Δ
unittests	?

Flags with carried forward coverage won't be shown. Click here to find out more.

see 570 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[kumare3]

Stopped sounds weird to be running

[EngHabu]

It's not currently being used in the operator... so I took a guess it's a temporary state (Succeeded/Failed are terminal)... hence why I marked it as Running. That said, I think it's ok for now to add it to the default handler of failing as an unknown/not handled state..