Html page redesign

[TillK17]

Context

AI/ai-sdk-java-backlog#I128

I have redesigned the Frontend of our sample app, including endpoint descriptions (based on JavaDoc), JSON rendering (GitHub Repo of tool), toggling between full json view or only showing response message (for calls to LLM with message output), streaming functionality and minimal error handling.

Feature scope:

• Prettify the page to look like an actual modern web page
  • Claude is your friend for this 😉
• Add descriptions for endpoints (add links, what is OpenAI, what is orchestration service, "here we try to trigger a content filter expecting the following result")
• Render response text content instead of plain JSON response

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

[TillK17]

• I would especially be interested in feedback regarding the explanation of the different API parts as many of you are most likely able to explain them better than me
• as there is no final decision on our new logo yet, I've agreed with @jjtang1985 to add this later

[TillK17]

• last commit is adapted to new backend of sample app with differentiation of JSON or content response by header field in request
• global toggle to switch between JSON rendering or plain text output
• not tested with new backend

[Jonas-Isr]

I merged the current state into this branch and fixed the behavior regarding the new backend. I also added minor improvements to the code.

[rpanackal]

Suggested change

	Create and delete a deployment with the Java specific configuration ID.
	Create a deployment for a configuration ID and delete after.

Reasoning below.

[rpanackal]

Suggested change

	Stop all deployments with the Java specific configuration ID. Only RUNNING deployments can be STOPPED.
	Stop all deployments with a specific configuration ID. Only RUNNING deployments can be STOPPED.

Configurations IDs are not tied to any language. Configurations listed are scoped under a resource group only.

Apart from that, I think, we should keep these details that are specific to our e2e test setup in aicore instance away from any user. I would remove it from all endpoint docs. Please get a second opinion about this.

[TillK17]

• have integrated most of @rpanackal feedback
• first two comments that arent resolved yet are fine for me, I dont really have an opinion wether we should remove e2e test setup related details, it should just be aligned with JavaDoc of controllers
• last open comment is resolved in 2 latest commits (as I wasn't sure about changing the Orchestration Controller JavaDoc, I did it in a seperate commit)

[rpanackal]

Looks good to me.