[8.8] Update APM links (elastic#156460) (elastic#156462)

# Backport

This will backport the following commits from `main` to `8.8`:
- [Update APM links
(elastic#156460)](elastic#156460)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Brandon
Morelli","email":"[email protected]"},"sourceCommit":{"committedDate":"2023-05-03T01:42:18Z","message":"Update
APM links (elastic#156460)\n\nThis PR updates three APM links. For the failing
links
in\r\nhttps://github.com/elastic/apm-server/pull/10560.","sha":"72c5d5286a651d8c4a3f7b9268a142270c7c3310","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.8.0","v8.9.0"],"number":156460,"url":"https://github.com/elastic/kibana/pull/156460","mergeCommit":{"message":"Update
APM links (elastic#156460)\n\nThis PR updates three APM links. For the failing
links
in\r\nhttps://github.com/elastic/apm-server/pull/10560.","sha":"72c5d5286a651d8c4a3f7b9268a142270c7c3310"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/156460","number":156460,"mergeCommit":{"message":"Update
APM links (elastic#156460)\n\nThis PR updates three APM links. For the failing
links
in\r\nhttps://github.com/elastic/apm-server/pull/10560.","sha":"72c5d5286a651d8c4a3f7b9268a142270c7c3310"}}]}]
BACKPORT-->

Co-authored-by: Brandon Morelli <[email protected]>

docs/apm/troubleshooting.asciidoc

@@ -93,8 +93,8 @@ Instead, we should strip away the unique information and group our transactions
 In this case, that means naming all blog transactions, `/blog`, and all documentation transactions, `/guide`.
 
 If you feel like you'd be losing valuable information by following this naming convention, don't fret!
-You can always add additional metadata to your transactions using {apm-guide-ref}/metadata.html#labels-fields[labels] (indexed) or
-{apm-guide-ref}/metadata.html#custom-fields[custom context] (non-indexed).
+You can always add additional metadata to your transactions using {apm-guide-ref}/data-model-metadata.html#data-model-labels[labels] (indexed) or
+{apm-guide-ref}/data-model-metadata.html#data-model-custom[custom context] (non-indexed).
 
 After ensuring you've correctly named your transactions,
 you might still see errors in the APM app related to transaction group limit reached:
@@ -167,7 +167,7 @@ see <<no-apm-data-found>> for further troubleshooting.
 *Ensure a field is searchable*
 There are two things you can do to if you'd like to ensure a field is searchable:
 
-1. Index your additional data as {apm-guide-ref}/metadata.html[labels] instead.
+1. Index your additional data as {apm-guide-ref}/data-model-metadata.html[labels] instead.
 These are dynamic by default, which means they will be indexed and become searchable and aggregatable.
 
 2. Create a custom mapping for the field.