DOC-689 | Fix toolchain, improve cURL example rendering

[Simran-B]

Description

• Fix toolchain failing to start because the wrong address is probed
• Fix handling of release images so that arangodb/enterprise images can be used without toolchain errors
• Fix examples: batch import, collection responsibleShard, async jobs
• Fix curl example rendering

Upstream PRs

• 3.10: arangodb/enterprise:3.10.14
• 3.11: arangodb/enterprise:3.11.8.2
• 3.12: arangodb/enterprise:3.12.0.2
• 3.13: arangodb/enterprise-preview:devel-nightly

[arangodb-docs-automation]

Deploy Preview Available Via
https://deploy-preview-538--docs-hugo.netlify.app

[Simran-B]

/generate-commit

[Simran-B]

/generate-commit

[Simran-B]

/generate-commit

[Simran-B]

/generate-commit

[Simran-B]

/generate-commit

[Simran-B]

/generate-commit

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: CircleCI Job.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email email@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: CircleCI Job.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email email@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails