[Core] Propogate InvalidArgument Status from LabelSelector Data Type

[ryanaoleary]

Why are these changes needed?

This PR is a follow-up to this comment: #51901 (comment). This PR changes the cluster resource scheduler to propagate a Ray status to ComputeResources in TaskSpecification when the LabelSelector data type is initialized. This allows a task built with a malformed label selector to return an error as a more useful Python exception rather than crashing Ray components in the C++.

Related issue number

#51564

Checks

• I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
• I've run scripts/format.sh to lint the changes in this PR.
• I've included any doc changes needed for https://docs.ray.io/en/master/.
  • I've added any new APIs to the API Reference. For example, if I added a
    method in Tune, I've added it in doc/source/tune/api/ under the
    corresponding .rst file.
• I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
• Testing Strategy
  • Unit tests
  • Release tests
  • This PR is not tested :(

[ryanaoleary]

cc: @dayshah, this is the follow-up to your comment on my previous PR. I have this marked as a draft currently because I'm still figuring out how to propagate the status from the TaskSpecification constructor call to submit_task in ray/python/ray/_raylet.pyx so that it's shown in the Python.