RayService: Omits Min and Max replicas from hash calculation

[kpitzen]

Why are these changes needed?

Currently, when updating RayService config, changing MinReplicas or MaxReplicas in the autoscaling config triggers an entirely new RayCluster to be instantiated. In order to facilitate orchestrating canary deployments, we'd like to have the ability to scale those parameters on an existing cluster as we move traffic over.

Related issue number

Currently no issue linked, but I can create one if needed.

Checks

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

[kousun12]

would love to see this in the next release