Allow script to have string or object value

[l-trotta]

Originally reported as a Java Client issue.

PutScript API support either the source of the script as a string, or as a Search Template object, which is equivalent to the whole SearchRequest body.

Since the Search Request body is also needed by Multisearch, it was extracted as a separate class in the search package to that both Multisearch and StoredScript can use it (it was also ordered alphabetically).

source in StoredScript is now an externally tagged union. (potentially breaking for generators)

Ideally nothing else should be changed in the client codes as a result of this PR except for StoredScript, I'm setting this up as a draft for now, let me know when the generators are ready.

[github-actions]

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

API	Status	Request	Response
msearch	🟢	17/17	16/16
search	🔴	2204/2262	2243/2244

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

[pquentin]

Since this does not affect elasticsearch-py, I'm approving.

However since it could affect elasticsearch-dsl-py, I added @miguelgrinberg to the list of reviewers.

[miguelgrinberg]

LGTM. And the Python DSL client is not affected by this change.

[l-trotta]

thank you both! I'll remember the python dsl for future issues

[JoshMock]

Shouldn't cause any issues for the JS generator either. 👍

[flobernd]

The same change should be applied to Script.source, RenderSearchTemplate.source, PhraseSuggestCollateQuery.source (and probably more places).

[github-actions]

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

API	Status	Request	Response
msearch	🟢	17/17	16/16
search	🔴	2320/2404	2387/2388

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
msearch_template	🟢	1/1	1/1
msearch	🟢	17/17	16/16
render_search_template	🟢	1/1	1/1
search_template	🟢	2/2	1/1
search	🔴	2320/2404	2387/2388
watcher.ack_watch	🟢	1/1	1/1
watcher.activate_watch	🟢	1/1	1/1
watcher.deactivate_watch	🟢	1/1	1/1
watcher.delete_watch	🟢	2/2	2/2
watcher.execute_watch	🟢	7/7	7/7
watcher.get_settings	⚪	Missing test	Missing test
watcher.get_watch	🟢	9/9	9/9
watcher.put_watch	🔴	29/38	38/38
watcher.query_watches	⚪	Missing test	Missing test
watcher.start	🟢	1/1	1/1
watcher.stats	🟢	1/1	1/1
watcher.stop	🟢	1/1	1/1
watcher.update_settings	⚪	Missing test	Missing test

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

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