Add details on error upon starting GraalVM native image built with Spring Native

[hypr2771]

What does this PR do? What is the motivation?

I personally faced an issue when running an image following exactly instructions in the DataDog documentation.
I could not find my error on Google anywhere else, apart from the official DataDog documentation, which was mentioning it and suggesting an outdated fix (was not working).

I had to look at the underlying building library to search for open issues, which is not necessarily a simple task to anyone since the place to search for is not that straightforward.

I suggest we report the fix suggested in the related repository to official documentation to ease troubleshooting.

Merge instructions

Maybe check whether the issue is closed and the latest release is available. In such case, we should probably change wording to mention we simply need to update to latest version instead of providing a fix.

Merge readiness:

• Ready for merge

For Datadog employees:

Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.

Additional notes

[brett0000FF]

@hypr2771 - Thanks for the detailed info and suggested content! I'm going to run this by engineering and do some light editing (e.g., I think we should still keep the info about the Paketo buildpack for versions older than 4.6.0, and then create a new section for this issue). Thanks!

[brett0000FF]

@hypr2771 - Thanks again for this info! I validated it and did a quick edit to keep the "older than 4.6.0" section separate from this new one. Appreciate you contributing to our docs! 🚀

[hypr2771]

@hypr2771 - Thanks for the detailed info and suggested content! I'm going to run this by engineering and do some light editing (e.g., I think we should still keep the info about the Paketo buildpack for versions older than 4.6.0, and then create a new section for this issue). Thanks!

Sure, it seemed pointless to me to indicate to upgrade to a version higher than 4.6.0 since it would have contained the same issue.
Anyway, glad it helped!