[autoscaler] Set new_config logging to debug in autoscaler (#38729)

Currently, it's really hard to debug autoscaler failures using monitor.out as it logs redundant new_config continuously in recent change. Fix is to move from print to DEBUG

ubuntu@ip-10-0-143-38:~$ ls -lah /tmp/ray/session_latest/logs/monitor*
-rw-rw-r-- 1 ubuntu ubuntu 2.2K Aug 22 01:19 /tmp/ray/session_latest/logs/monitor.err
-rw-rw-r-- 1 ubuntu ubuntu 7.8M Aug 22 16:23 /tmp/ray/session_latest/logs/monitor.log
-rw-rw-r-- 1 ubuntu ubuntu 124M Aug 22 16:23 /tmp/ray/session_latest/logs/monitor.out
Related issue number
"Closes #38727"

---------

Signed-off-by: maheedhar reddy chappidi <chappidm@amazon.com>

Author: chappidim

python/ray/autoscaler/_private/autoscaler.py

@@ -1036,7 +1036,10 @@ def reset(self, errors_fatal=False):
                         "available until you upgrade ray on your cluster.",
                         exc_info=e,
                     )
-            print("new config", new_config, type(new_config))
+            logger.debug(
+                f"New config after validation: {new_config},"
+                f" of type: {type(new_config)}"
+            )
             (new_runtime_hash, new_file_mounts_contents_hash) = hash_runtime_conf(
                 new_config["file_mounts"],
                 new_config["cluster_synced_files"],