chore: [Orchestration] Add warning for incompatible API usage

[newtork]

Context

Related

• Structured Output - Feedback #615
• https://github.com/SAP/ai-sdk-java-backlog/issues/315

Considering a warn message, since we cannot enforce it via API design with the existing code.

Feature scope:

• Log warning for incorrect API usage: Spring AI .entity(..) + Orchestration .withTemplateConfig(..)

Definition of Done

• Functionality scope stated & covered
• Tests cover the scope above
• Error handling created / updated & covered by the tests above
• Aligned changes with the JavaScript SDK
• Documentation updated
• Release notes updated

[Jonas-Isr]

I am not sure if testing just for https://json-schema.org/draft/2020-12/schema is good here. This might lead to false positives if a users specifies the schema version in their actual prompt (not sure how likely it is, but might happen?!)

I would thus add a bit of the formatting around it to the test string.

Suggested change

	val JSON_SCHEMA = "https://json-schema.org/draft/2020-12/schema";
	if (t.text().contains(JSON_SCHEMA) && config.getTemplateConfig() != null) {
	log.warn("Combination of `entity(...)` and `withTemplateConfig(...)` is not supported.");
	}
	val JSON_SCHEMA = "\\n \\\"$schema\\\" : \\\"https://json-schema.org/draft/2020-12/schema\\\",";
	if (t.text().contains(JSON_SCHEMA) && config.getTemplateConfig() != null) {
	log.warn("Combination of `entity(...)` and `withTemplateConfig(...)` is not supported.");
	}

[newtork]

Likely we shouldn't put this in OrchestrationClient altogether. If we put this into code, it'd be better located in Spring AI related class(es) 🤔