Fix placeholder links for security

[vishaangelova]

This is a sub-issue of #1734, and the aim is to address the possibility of malicious dummy links in docs by adding a warning in the related Admin docs.

Parent issue description

For security reasons, we plan to replace any placeholder/fake URLs with non-hostable placeholder segments.

Remove segments that make a valid URL, including prefixes (http://) and TLDs (.com).

before:

<script src="https://<your-cdn-host>.com/path/to/elastic-apm-rum.umd.min-<version>.js" crossorigin></script>

after:

<script src="<your-url>/elastic-apm-rum.umd.min-<version>.js" crossorigin></script>

The placeholder <> can be adapted to use descriptive text for its purpose. For example, a placeholder for a splunk server might look like this:

server: <your-splunk-server-url>/<path>

[shainaraskas]

looking into alternatives in the parent issue

[shainaraskas]

ready

[kilfoyle]

PRs:

• curator: Replace placeholder URLs curator#1771
• kibana: [Docs] Replace placeholder URLs kibana#228063
• elasticsearch: [Docs] Replace placeholder URLs elasticsearch#131309
• docs-content: Replace placeholder URLs #2141

Nothing to fix in: cloud, ecctl, cloud-on-k8s

Note: For cloud, there are 28 URLs like https://$COORDINATOR_HOST:12443/api/v1/deployments/$DEPLOYMENT_ID. I left these as is because we advise users to export the $COORDINATOR_HOST and $DEPLOYMENT_ID ID variables for the examples to work. Adding angle brackets would break that.