[stevehu]

Generated producer, consumer and Streams templates show the invalid endpoint-identification algorithm algo-name in commented TLS examples. Use https consistently with the corrected light-kafka defaults. Related: networknt/light-kafka#265.

Keep these optional lines commented and retain the existing external override keys. Extend the existing real generation regression for both server/service generators and all eight Kafka flag combinations to check the emitted TLS examples, default injection and explicit empty opt-out. Document migration of previously uncommented examples and invalid overrides.

Validation on JDK 25.0.3 with the existing Maven cache:

• Full mvn -o -q clean install: 65 tests, zero failures/errors, 6 skipped.
• Focused hybrid reactor validation also passed: 13 tests, no failures/errors/skips.
• git diff --check passed; staged impact analysis reports low risk.

No production Java, dependency, workflow or schema-registration changes are included. The actual hostname match/mismatch handshake fixture is in the companion light-kafka PRs. light-example-4j is excluded; no deployment is included. Remote CI remains separate from local evidence.

Companion PRs:

• networknt/light-kafka (2.x): Fix Kafka SSL endpoint identification defaults (2.x) light-kafka#269
• networknt/light-codegen (master): Use https in generated Kafka TLS examples #740
• networknt/kafka-sidecar (2.x): Fix Kafka TLS endpoint identification defaults (2.x) kafka-sidecar#207