Misc edit to keep an AZLOG_INFO instead of AZPrint. No real difference, but good as an example for pytest

Signed-off-by: Gene Walters <genewalt@amazon.com>

AutomatedTesting/Gem/PythonTests/EditorPythonTestTools/editor_python_test_tools/utils.py

@@ -114,7 +114,7 @@ class TestHelper:
 
             wait_for_critical_expected_line("Editor is sending the editor-server the level data packet.", section_tracer.prints, 5.0)
 
-            wait_for_critical_expected_line("MultiplayerEditorConnection: Editor Server completed receiving the editor's level assets, responding to Editor...", section_tracer.prints, 5.0)
+            wait_for_critical_expected_line("Logger: Editor Server completed receiving the editor's level assets, responding to Editor...", section_tracer.prints, 5.0)
 
             wait_for_critical_expected_line("Editor-server ready. Editor has successfully connected to the editor-server's network simulation.", section_tracer.prints, 5.0)
 

Gems/Multiplayer/Code/Source/Editor/MultiplayerEditorConnection.cpp

@@ -160,7 +160,8 @@ namespace Multiplayer
             }
             
             networkInterface->Listen(sv_port);
-            AZ_Printf("MultiplayerEditorConnection", "Editor Server completed receiving the editor's level assets, responding to Editor...\n")
+            
+            AZLOG_INFO("Editor Server completed receiving the editor's level assets, responding to Editor...\n")
             return connection->SendReliablePacket(MultiplayerEditorPackets::EditorServerReady());
         }