Fix: Add EnvironmentPostProcessor for conditional RabbitMQ/Kafka exclusion

[casc84ab]

Summary

• Add FireflyEdaEnvironmentPostProcessor that excludes RabbitMQ and Kafka auto-configurations when neither publisher nor consumer properties are enabled
• Prevents health check errors for unconfigured messaging infrastructure at startup
• Configuration-driven approach via application.yml properties

Test plan

• All 1,248 framework tests pass
• 29/36 microservices start cleanly with zero RabbitMQ warnings
• No duplicate bean registrations detected

[ancongui]

LGTM. This is the most substantial change in the series, but well-implemented:

Architecture: Using EnvironmentPostProcessor (registered via spring.factories) is the correct approach for conditionally excluding auto-configurations early in the startup lifecycle — before bean definitions are created.

Logic: The exclusion logic correctly:

• Checks both publisher and consumer properties for each transport (RabbitMQ/Kafka)
• Respects explicit Spring Boot native configuration (spring.rabbitmq.host, spring.kafka.bootstrap-servers) as an override
• Preserves any existing spring.autoconfigure.exclude entries
• Uses addFirst priority so application properties can still override

pom.xml: Removing "Optional" comments from Kafka/RabbitMQ dependencies makes sense — they need to be on the compile classpath for the post-processor, with runtime exclusion now handled programmatically.

Registration: spring.factories is still the correct registration mechanism for EnvironmentPostProcessor in Spring Boot 3.x (unlike auto-configurations which migrated to .imports).