refactor: Set logging to INFO level for production-like behavior

Changed default logging levels to INFO for production-oriented example:
- Removed DEBUG level for io.a2a.examples.cloud
- Removed DEBUG level for io.a2a.server.events
- Removed DEBUG level for io.a2a.extras.queuemanager.replicated
- Removed DEBUG level for io.a2a.server.requesthandlers

Added documentation comments showing how to enable DEBUG logging for
troubleshooting specific components.

This follows best practices for production examples while maintaining
clear guidance for developers who need detailed logs during development.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Author: kabir

examples/cloud-deployment/server/src/main/resources/application.properties

@@ -36,12 +36,14 @@ mp.messaging.incoming.replicated-events-in.value.deserializer=org.apache.kafka.c
 mp.messaging.incoming.replicated-events-in.auto.offset.reset=earliest
 
 # Logging
+# Default to INFO level for production-like behavior
+# To enable DEBUG logging for troubleshooting, set these to DEBUG:
+#   quarkus.log.category."io.a2a.examples.cloud".level=DEBUG
+#   quarkus.log.category."io.a2a.server.events".level=DEBUG
+#   quarkus.log.category."io.a2a.extras.queuemanager.replicated".level=DEBUG
+#   quarkus.log.category."io.a2a.server.requesthandlers".level=DEBUG
 quarkus.log.level=INFO
 quarkus.log.category."io.a2a".level=INFO
-quarkus.log.category."io.a2a.examples.cloud".level=DEBUG
-quarkus.log.category."io.a2a.server.events".level=DEBUG
-quarkus.log.category."io.a2a.extras.queuemanager.replicated".level=DEBUG
-quarkus.log.category."io.a2a.server.requesthandlers".level=DEBUG
 quarkus.log.console.format=%d{HH:mm:ss} %-5p [%c{2.}] (%t) %s%e%n
 
 # Health checks