Kafka container should not be required in some tests

[qmonmert]

Fix #31133

[mshima]

See https://github.com/jhipster/generator-jhipster/actions/runs/20666629893/job/59344143827?pr=31863.
Backend test is taking 10 minutes. It's probably probing Kafka server.

[qmonmert]

Before

After

[qmonmert]

@mshima WDYT?

[mshima]

@ActiveProfiles("kafka") doesn’t work?
Instead of loading the file manually?

[Copilot]

Pull request overview

This PR addresses issue #31133 by making Kafka test containers optional rather than required for all tests. The changes enable tests to use Spring Cloud Stream's in-memory TestChannelBinder by default, only requiring Kafka-specific configuration when explicitly opted in via the @EmbeddedKafka annotation.

Changes:

• Removed automatic @EmbeddedKafka annotation from all integration tests
• Modified test configuration to disable Kafka by default and use test binder
• Created separate application-kafka.yml profile for Kafka-enabled tests
• Updated context customizer to load Kafka config only when @EmbeddedKafka is present

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
KafkaTestContainersSpringContextCustomizerFactory.java.ejs	Changed from starting Kafka containers to loading application-kafka.yml when @embeddedkafka is detected
generator.ts	Removed automatic @embeddedkafka annotation addition to integration tests
generator.spec.ts.snap	Updated snapshot to reflect removal of automatic @embeddedkafka annotation
application.yml.ejs	Disabled Kafka by default: excluded KafkaAutoConfiguration, disabled function scanning, set test binder as default
application-kafka.yml.ejs	New file containing Kafka-specific configuration (function definitions and bindings) loaded when @embeddedkafka is used
files.ts	Added conditional generation of application-kafka.yml for Kafka-enabled projects

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Wrapping the IOException in a RuntimeException loses the specific exception type. Consider using a more specific exception or providing more context in the RuntimeException message to aid debugging. For example, you could use: throw new RuntimeException("Failed to load application-kafka.yml configuration file", e)

Suggested change

	throw new RuntimeException(e);
	throw new RuntimeException("Failed to load application-kafka.yml configuration file", e);

[mshima]

Kafka testcontainer doesn't seem to be started at all.
Test doesn’t seem to be functional, wonder if it’s already problematic in main.

[DanielFran]

Superseded by #32079

[mshima]

Still relevant.