docs: Update and combine troubleshooting guides

[bmorelli25]

Summary

This PR updates and combines the APM troubleshooting guides.

Preview this PR:

• Troubleshoot
  • Common problems
  • What happens when APM Server or Elasticsearch is down?
  • APM Server response codes
  • Processing and performance
  • APM Server binary debugging

[mergify]

This pull request does not have a backport label. Could you fix it @bmorelli25? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-7.x is the label to automatically backport to the 7.x branch.
• backport-7./d is the label to automatically backport to the 7./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

[ghost]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-05-19T01:17:01.820+0000

• Duration: 2 min 59 sec

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate and publish the docker images.

• /test windows : Build & tests on Windows.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[bmorelli25]

@elasticmachine, run elasticsearch-ci/docs

[bmorelli25]

@elasticmachine, run elasticsearch-ci/docs

[bmorelli25]

@elasticmachine, run elasticsearch-ci/docs

[simitt]

@elasticmachine, run elasticsearch-ci/docs

[mergify]

This pull request is now in conflicts. Could you fix it @bmorelli25? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b ft-troubleshoot upstream/ft-troubleshoot
git merge upstream/main
git push upstream ft-troubleshoot

[axw]

The "SSL client fails to connect" section is pretty weird IMO. I realise it's preexisting, but I don't think I've ever read it before. Why use telnet to debug? How does one "Verify that the certificate is valid and that the hostname and IP match."?

I guess leave this as a followup, but perhaps we should just suggest that users run curl to check they can make a request to the server?

[bmorelli25]

Thanks. I'll open an issue to address this.