Protect against stackoverflow when printing advice exceptions

[JonasKunz]

What does this PR do?

Tries to mitigate #3152 .

Checklist

• This is a bugfix
  • I have updated CHANGELOG.asciidoc
  • I have added tests that would fail without this fix not feasible to produce a StackOverflow in a test while keeping the system in a known state.

[apmmachine]

💚 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-06-07T11:59:57.144+0000

• Duration: 19 min 55 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• run benchmark tests : Run the benchmark tests.

• run jdk compatibility tests : Run the JDK Compatibility tests.

• run integration tests : Run the Agent Integration tests.

• run end-to-end tests : Run the APM-ITs.

• run windows tests : Build & tests on windows.

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

[github-actions]

/test

[jackshirazi]

Fine without a test but, if you feel like it, you could add a test with a non-tail recursive call that logs on each call until it hits actual stack overflow and confirm the expected "should never happen"