Pass endpoint_id and path_parts to transport

[pquentin]

As part of #2435, the transport needs to know the endpoint id and path parts, and can only get them from the client. This pull request makes sure to pass that info to the client.

There are two commits here:

• 5ff3169 (#2457) which accepts endpoint_id/path_parts in base clients, updates tests and depends on the main branch of elastic-transport
• 2ce3c32 (#2457) that runs code generation to define endpoint_id/path_parts in all APIs

This PR depends on elastic/elastic-transport-python#151.

I'm wondering about the type of those new parameters. The natural way in elastic-transport was str | DefaultType while here it's str | None. DEFAULT is a way to make None meaningful, but that's not needed here.

[github-actions]

A documentation preview will be available soon.

• 🔨 Buildkite builds
• 📚 HTML diff
• 📙 Preview page

Request a new doc build by commenting

• Rebuild this PR: run docs-build
• Rebuild this PR and all Elastic docs: run docs-build rebuild

_{run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.}

_{If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.}

[pquentin]

The previous approach was incorrect for a few reasons:

• the typing of endpoint_id and path_parts has to be fixed to match the definition in elastic-transport-python. It's not Optional, but Union[DefaultType, ...]. Maybe Optional was fine, we use both styles in the code, not sure why.
• the values should be quoted (so that eg. ["a", "b"] becomes "a,b")
• we should only pass values that are set, indeed many APIs have multiple forms, like _cat/recovery and _cat/recovery/{index}

The last two can be solved by defining __path_parts alongside __path, like this:

if index not in SKIP_IN_PATH:
    __path_parts = {"index": _quote(index)}
    __path = f"/_cat/recovery/{__path_parts['index']}"
else:
    __path_parts = {}
    __path = "/_cat/recovery"

The above has been implemented now.

[xrmx]

I vaguely remember some pain in specifying git urls without an hash, like when trying to upgrade a package checked out from git.
BTW you didn't release a elastic-transport-python because you want to check that all layers are working right?

[pquentin]

That's right. I don't intend to release anything with git dependencies. Maybe I should use a pre-release instead though!

[github-actions]

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

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

[github-actions]

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

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

[pquentin]

8.13 backport is #2468. This should not be backported to 8.12, I nearly forgot.