docs: add Linux capabilities config for pyroscope.java

[marcsanmi]

PR Description

Update pyroscope.java documentation to include information on configuring Linux capabilities when running in Kubernetes environments. This addition helps users properly set up Alloy with the necessary permissions for Java process profiling in environments where Linux capabilities are enforced.

Which issue(s) this PR fixes

Closes #1616

Notes to the Reviewer

PR Checklist

• CHANGELOG.md updated
• Documentation added
• Tests updated
• Config converters updated

[knylander-grafana]

Thank you for updating doc. Do we need to backport?

[marcsanmi]

Thank you for updating doc. Do we need to backport?

Yes, I added the corresponding labels. Thanks!

[Rperry2174]

@marcsanmi can we also add this somewhere to a couple other places:

1. Examples - this is often where I send people when they want something to just copy and paste.. I think having this information in the readme will be helpful for people who are looking to copy and paste from examples rather than using docs
2. Pyroscope java docs - even though we are duplicating this to multiple places I thin its probably likely that many poeople expect everything they need to know will be on this page .. we should at least mention it

Again even though we are duplicating this in a couple places we often have many paths through which people enter the docs and having this key information at least mentioned everywhere is important

[knylander-grafana]

@marcsanmi can we also add this somewhere to a couple other places:

1. Examples - this is often where I send people when they want something to just copy and paste.. I think having this information in the readme will be helpful for people who are looking to copy and paste from examples rather than using docs
2. Pyroscope java docs - even though we are duplicating this to multiple places I thin its probably likely that many poeople expect everything they need to know will be on this page .. we should at least mention it

Again even though we are duplicating this in a couple places we often have many paths through which people enter the docs and having this key information at least mentioned everywhere is important

Do we need to duplicate the exact documentation with no changes? If so, we can consider sharing content between repositories. For example, store the source doc in the Alloy repo and then include that source doc in one or more other locations using an include statement.

[marcsanmi]

As discussed in grafana/pyroscope#3599 (comment), it doesn't make sense to add this documentation in pyroscope examples since this related to Alloy's chart configuration.

cc @Rperry2174 @knylander-grafana

[clayton-cornell]

One minor tweak - use of whitelist and it's good from my side :-)

[clayton-cornell]

Is this one ready to be merged as-is?

[marcsanmi]

Is this one ready to be merged as-is?

Yes 👍