docs: ebpf-otel fixes

[korniltsev]

• use one dockerfile, build the profiler in the dockerfile, remove prerequisites to build the profiler and copy the profiler separately
• add screenshot
• fix profiler,pyroscope,collector versions. It does not work on the latests.

Notes: ebpf profiler does not properly work in minikube. I've tested in a real k8s cluster by pushing an image to the public docker repo. I am not sure we should advertise minikube in the example if it does not work. We can consider submiting a PR with pid namespace inspection from pyroscope ebpf profiler.

[github-actions]

This PR must be merged before a backport PR will be created.

[github-actions]

This PR must be merged before a backport PR will be created.

[github-actions]

This PR must be merged before a backport PR will be created.

[knylander-grafana]

Thank you for updating the readmes and the examples. Approving the readme changes.

[marcsanmi]

LGTM 👍

[marcsanmi]

I like this. However, I think we should update to avoid working with pinned versions and images once the profiler is stable enough

[github-actions]

The backport to release/v1.9 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-3777-to-release/v1.9 origin/release/v1.9
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x a2c06eeb4719429993c82a486c94a86785161d1c

When the conflicts are resolved, stage and commit the changes:

git add . && git cherry-pick --continue

If you have the GitHub CLI installed:

# Push the branch to GitHub:
git push --set-upstream origin backport-3777-to-release/v1.9
# Create the PR body template
PR_BODY=$(gh pr view 3777 --json body --template 'Backport a2c06eeb4719429993c82a486c94a86785161d1c from #3777{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title '[release/v1.9] docs: ebpf-otel fixes' --body-file - --label 'type/docs' --label 'backport' --base release/v1.9 --milestone release/v1.9 --web

Or, if you don't have the GitHub CLI installed (we recommend you install it!):

# Push the branch to GitHub:
git push --set-upstream origin backport-3777-to-release/v1.9

# Create a pull request where the `base` branch is `release/v1.9` and the `compare`/`head` branch is `backport-3777-to-release/v1.9`.

# Remove the local backport branch
git switch main
git branch -D backport-3777-to-release/v1.9

[github-actions]

The backport to release/v1.10 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-3777-to-release/v1.10 origin/release/v1.10
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x a2c06eeb4719429993c82a486c94a86785161d1c

When the conflicts are resolved, stage and commit the changes:

git add . && git cherry-pick --continue

If you have the GitHub CLI installed:

# Push the branch to GitHub:
git push --set-upstream origin backport-3777-to-release/v1.10
# Create the PR body template
PR_BODY=$(gh pr view 3777 --json body --template 'Backport a2c06eeb4719429993c82a486c94a86785161d1c from #3777{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title '[release/v1.10] docs: ebpf-otel fixes' --body-file - --label 'type/docs' --label 'backport' --base release/v1.10 --milestone release/v1.10 --web

Or, if you don't have the GitHub CLI installed (we recommend you install it!):

# Push the branch to GitHub:
git push --set-upstream origin backport-3777-to-release/v1.10

# Create a pull request where the `base` branch is `release/v1.10` and the `compare`/`head` branch is `backport-3777-to-release/v1.10`.

# Remove the local backport branch
git switch main
git branch -D backport-3777-to-release/v1.10