feat(RHOAIENG-26590): Report RayJob status via SDK

[chipspeak]

Issue link

Jira

What changes have been made

Reporting RayJob status in the SDK using similar logic to RayCluster status reporting.

Verification steps

1. Follow the same steps as in the previous feature PR
2. Once the job has been submitted run rayjob.status() to observe the status output.

Checks

• I've made sure the tests are passing.
• Testing Strategy
  • Unit tests
  • Manual tests
  • Testing is not required for this change

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.06%. Comparing base (bfff951) to head (d1be9e8).
⚠️ Report is 1 commits behind head on ray-jobs-feature.

Additional details and impacted files

@@                 Coverage Diff                  @@
##           ray-jobs-feature     #868      +/-   ##
====================================================
+ Coverage             92.64%   93.06%   +0.41%     
====================================================
  Files                    26       28       +2     
  Lines                  1427     1513      +86     
====================================================
+ Hits                   1322     1408      +86     
  Misses                  105      105              

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[chipspeak]

/hold

[pawelpaszki]

I verified the behaviour. it works as per the verification steps. thanks @chipspeak !

[kryanbeane]

other than my one comment re naming conventions, which the more I think about it, could be a one story pointer we do afterwards this is great. thanks Pat 🥇

[kryanbeane]

lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kryanbeane

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [kryanbeane]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[chipspeak]

/cancel

[chipspeak]

/unhold

[chipspeak]

/woof

[openshift-ci]

@chipspeak:

In response to this:

/woof

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.