[Serve] use serve logger name for logs in serve

[GeneDer]

Why are these changes needed?

Some Serve logs are not using the configured ray.serve logger, so the logs are redirected to the root logger and can cause unwanted logs to be logged to the terminal when running Serve. This PR ensure all the logger in Serve are using ray.serve logger to log messages.

Tested in premerge using runtime wheel and not seeing the unwanted logs anymore:

Also note this is how it looks without the change:

Related issue number

Closes: https://github.com/anyscale/ray-llm/issues/1962

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 :(

[edoakes]

Do we not need to go through the get_component_logger to set up logging configuration for these?

[GeneDer]

Do we not need to go through the get_component_logger to set up logging configuration for these?

I think in general cases ray.serve logger is setup together with controller. But I think this is a good point if those modules are imported and used outside of serve, then the ray.serve logger might not already be setup and will still fallback to the root logger. Let me do some more experiment, maybe we just need to setup a default ray.serve logger at import time.