Why are these changes needed?

• This pull request updates the comment for the disable_launch_config_check setting in autoscaler.py to provide a clearer explanation, aligning it with the description found inscheduler.py.
• The goal is to clarify the purpose of the disable_launch_config_check setting specifically in the context of StandardAutoscaler. This change enhances the understanding of its purpose and usage scenarios.
• Additionally, if logs are required when disable_launch_config_check is enabled, similar to the behavior in scheduler.py, they will be added to functions in autoscaler.py. This change improves clarity regarding its purpose and usage scenarios.

Related issue number

Checks

• I've signed off every commit(by using the -s flag, i.e.,git commit -s) in this PR.
• I've runscripts/format.sh to lint the changes in this PR.
• I've included any doc changes needed forhttps://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 indoc/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 athttps://flakey-tests.ray.io/
• Testing Strategy
  • Unit tests
  • Release tests
  • This PR is not tested :(