Add integration test for kuberay ray service and improve ray service operator

[brucez-anyscale]

Why are these changes needed?

This pr adds basic integration test for ray service.
This pr also add requeue time for ray service controller to make it more responsible.
The k8s reconciler handles error in a backoff manner, which will make it reconcile once per several mins.
To avoid that, for reconcileServe, we do not return err but a requeue time to improve the overall RayService Experience.
Also change one status naming to make it less frightening.

Related issue number

Checks

• I've made sure the tests are passing.
• Testing Strategy
  • Unit tests
  • Manual tests
  • This PR is not tested :(

[DmitriGekhtman]

It appears there are some changes not related to testing.
Could you explain those changes in the PR description?

[brucez-anyscale]

It appears there are some changes not related to testing. Could you explain those changes in the PR description?

Thanks. Add more info.

[DmitriGekhtman]

Looks reasonable.
@simon-mo should also review

[simon-mo]

@wilsonwang371 confirming this is the right place to add integration test?
Also cc @Jeffwan we want to make sure this part of the release criteria of the 0.3.

[wilsonwang371]

@wilsonwang371 confirming this is the right place to add integration test? Also cc @Jeffwan we want to make sure this part of the release criteria of the 0.3.

@brucez-anyscale How about adding another test file to do this? Or maybe we can file another PR later to separate these tests into different files and run them in parallel.

[brucez-anyscale]

@wilsonwang371 confirming this is the right place to add integration test? Also cc @Jeffwan we want to make sure this part of the release criteria of the 0.3.

@brucez-anyscale How about adding another test file to do this? Or maybe we can file another PR later to separate these tests into different files and run them in parallel.

sg. I think we can do it in another pr.