Add Azure OpenAI inference details

[lcawl]

Relates to #3821, elastic/elasticsearch#125187

This PR adds details and examples derived from https://www.elastic.co/guide/en/elasticsearch/reference/8.18/infer-service-azure-openai.html

[github-actions]

Following you can find the validation results for the APIs you have changed.

API	Status	Request	Response
inference.put_azureopenai	⚪	Missing test	Missing test
inference.put_openai	⚪	Missing test	Missing test

You can validate these APIs yourself by using the make validate target.

[github-actions]

Following you can find the validation results for the APIs you have changed.

API	Status	Request	Response
inference.put_azureopenai	⚪	Missing test	Missing test
inference.put_openai	⚪	Missing test	Missing test

You can validate these APIs yourself by using the make validate target.

[l-trotta]

I think text_embedding has some additional settings fields? https://github.com/elastic/elasticsearch/blob/ba2f7f606f71c8a8b0ff11f687858feba7655756/x-pack/plugin/inference/src/main/java/org/elasticsearch/xpack/inference/services/azureopenai/embeddings/AzureOpenAiEmbeddingsServiceSettings.java#L272 @jonathan-buttner we should also add dimensions, max_input_tokens and similarity right?

[jonathan-buttner]

Yeah dimensions would be a good one to add. @davidkyle what do you think about max_input_tokens and similarity? We default similarity if it isn't set during the request. I don't believe we've documented max_input_tokens before.

[lcawl]

Is this an appropriate description for the dimensions string?: https://platform.openai.com/docs/api-reference/embeddings/create#embeddings-create-dimensions

[jonathan-buttner]

Yep!

[l-trotta]

LGTM, to fix the merging issues please rebase onto main and regenerate the output - also the exported classes, it would be better to have them in a separate Settings file, if this is merged first then all the other PRs can be rebased over it and the exported classes can be moved in the new file

[github-actions]

Following you can find the validation results for the APIs you have changed.

API	Status	Request	Response
inference.put_azureopenai	⚪	Missing test	Missing test
inference.put_openai	⚪	Missing test	Missing test

You can validate these APIs yourself by using the make validate target.

[github-actions]

The backport to 8.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-8.x 8.x
# Navigate to the new working tree
cd .worktrees/backport-8.x
# Create a new branch
git switch --create backport-4019-to-8.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d5b1a529a13e4e8eabc56716ed86be6819bd0718
# Push it to GitHub
git push --set-upstream origin backport-4019-to-8.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-8.x

Then, create a pull request where the base branch is 8.x and the compare/head branch is backport-4019-to-8.x.

[github-actions]

The backport to 8.18 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-8.18 8.18
# Navigate to the new working tree
cd .worktrees/backport-8.18
# Create a new branch
git switch --create backport-4019-to-8.18
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d5b1a529a13e4e8eabc56716ed86be6819bd0718
# Push it to GitHub
git push --set-upstream origin backport-4019-to-8.18
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-8.18

Then, create a pull request where the base branch is 8.18 and the compare/head branch is backport-4019-to-8.18.

[github-actions]

The backport to 9.0 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-9.0 9.0
# Navigate to the new working tree
cd .worktrees/backport-9.0
# Create a new branch
git switch --create backport-4019-to-9.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d5b1a529a13e4e8eabc56716ed86be6819bd0718
# Push it to GitHub
git push --set-upstream origin backport-4019-to-9.0
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-9.0

Then, create a pull request where the base branch is 9.0 and the compare/head branch is backport-4019-to-9.0.

[lcawl]

💚 All backports created successfully

Status	Branch	Result
✅	9.0

Questions ?

Please refer to the Backport tool documentation

[lcawl]

💚 All backports created successfully

Status	Branch	Result
✅	8.x

Questions ?

Please refer to the Backport tool documentation

[lcawl]

💚 All backports created successfully

Status	Branch	Result
✅	8.18

Questions ?

Please refer to the Backport tool documentation