Add simulate.ingest specification

[lcawl]

Relates to #3377

This PR adds a missing specification based on https://www.elastic.co/guide/en/elasticsearch/reference/master/simulate-ingest-api.html
It also moves the existing simulate ingest example files to appropriate subfolders

[github-actions]

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

API	Status	Request	Response
ingest.delete_geoip_database	🟢	1/1	1/1
ingest.delete_ip_location_database	🟢	1/1	1/1
ingest.delete_pipeline	🟢	15/15	15/15
ingest.geo_ip_stats	🟢	1/1	1/1
ingest.get_geoip_database	🟢	6/6	6/6
ingest.get_ip_location_database	🟢	7/7	7/7
ingest.get_pipeline	🟢	22/22	22/22
ingest.processor_grok	🟢	1/1	1/1
ingest.put_geoip_database	🟢	3/3	3/3
ingest.put_ip_location_database	🟢	4/4	4/4
ingest.put_pipeline	🟢	60/60	60/60
ingest.simulate	🟢	10/10	10/10
simulate.ingest	🔴	11/12	12/12

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
ingest.delete_geoip_database	🟢	1/1	1/1
ingest.delete_ip_location_database	🟢	1/1	1/1
ingest.delete_pipeline	🟢	15/15	15/15
ingest.geo_ip_stats	🟢	1/1	1/1
ingest.get_geoip_database	🟢	6/6	6/6
ingest.get_ip_location_database	🟢	7/7	7/7
ingest.get_pipeline	🟢	22/22	22/22
ingest.processor_grok	🟢	1/1	1/1
ingest.put_geoip_database	🟢	3/3	3/3
ingest.put_ip_location_database	🟢	4/4	4/4
ingest.put_pipeline	🟢	60/60	60/60
ingest.simulate	🟢	10/10	10/10
simulate.ingest	🔴	11/12	12/12

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

[l-trotta]

I have 2 main doubts I need to clear with this one:

• Request: while everything looks good, it seems like the server processes all maps as Map<String, Map<String, Object>> rather then parsing the specific objects, leading to validation fails. we need to decide if we want to be generic in the same way.
• Response: the response does looks very similar to the SimulateDocumentResult class we have in the spec, but it slightly differs, so we should map it from scratch based on what the server outputs. I see that in the documentation there's an executed_pipelines field which I cannot find anywhere in the server code except for SimulateIndexResponse, which should be another case, could it be wrong?

[github-actions]

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

API	Status	Request	Response
ingest.delete_geoip_database	🟢	1/1	1/1
ingest.delete_ip_location_database	🟢	1/1	1/1
ingest.delete_pipeline	🟢	15/15	15/15
ingest.geo_ip_stats	🟢	1/1	1/1
ingest.get_geoip_database	🟢	6/6	6/6
ingest.get_ip_location_database	🟢	7/7	7/7
ingest.get_pipeline	🟢	22/22	22/22
ingest.processor_grok	🟢	1/1	1/1
ingest.put_geoip_database	🟢	3/3	3/3
ingest.put_ip_location_database	🟢	4/4	4/4
ingest.put_pipeline	🟢	60/60	60/60
ingest.simulate	🟢	10/10	10/10
simulate.ingest	🔴	11/12	12/12

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
ingest.delete_geoip_database	🟢	1/1	1/1
ingest.delete_ip_location_database	🟢	1/1	1/1
ingest.delete_pipeline	🟢	15/15	15/15
ingest.geo_ip_stats	🟢	1/1	1/1
ingest.get_geoip_database	🟢	6/6	6/6
ingest.get_ip_location_database	🟢	7/7	7/7
ingest.get_pipeline	🟢	22/22	22/22
ingest.processor_grok	🟢	1/1	1/1
ingest.put_geoip_database	🟢	3/3	3/3
ingest.put_ip_location_database	🟢	4/4	4/4
ingest.put_pipeline	🟢	60/60	60/60
ingest.simulate	🟢	10/10	10/10
simulate.ingest	🔴	11/12	12/12

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

[JoshMock]

my concerns are all addressed now. looks like you have a couple conflicts to work out, but otherwise LGTM.

[github-actions]

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

API	Status	Request	Response
ingest.delete_geoip_database	🟢	1/1	1/1
ingest.delete_ip_location_database	🟢	1/1	1/1
ingest.delete_pipeline	🟢	15/15	15/15
ingest.geo_ip_stats	🟢	1/1	1/1
ingest.get_geoip_database	🟢	6/6	6/6
ingest.get_ip_location_database	🟢	7/7	7/7
ingest.get_pipeline	🟢	22/22	22/22
ingest.processor_grok	🟢	1/1	1/1
ingest.put_geoip_database	🟢	3/3	3/3
ingest.put_ip_location_database	🟢	4/4	4/4
ingest.put_pipeline	🟢	60/60	60/60
ingest.simulate	🟢	10/10	10/10
simulate.ingest	🔴	11/12	12/12

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-3400-to-8.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 46b99ee0c07b9aabd0fa6f3dcdcc63738cb219d9
# Push it to GitHub
git push --set-upstream origin backport-3400-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-3400-to-8.x.

[github-actions]

The backport to 8.17 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.17 8.17
# Navigate to the new working tree
cd .worktrees/backport-8.17
# Create a new branch
git switch --create backport-3400-to-8.17
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 46b99ee0c07b9aabd0fa6f3dcdcc63738cb219d9
# Push it to GitHub
git push --set-upstream origin backport-3400-to-8.17
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-8.17

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

[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.17

Questions ?

Please refer to the Backport tool documentation