docs(examples): Add documentation for examples/tracing/golang-push

[simonswine]

As a follow up to #3765. I have slightly adapter the README. Let me know what you think. Maybe we should also update the others like that.

The README.md also mentions the opentracing spanprofiler, which we never activated, this will also active this part.

[kolesnikovae]

LGTM!

[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-3770-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 e10086d4a75091fefe16fbd365e8e576e9912bd5

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-3770-to-release/v1.9
# Create the PR body template
PR_BODY=$(gh pr view 3770 --json body --template 'Backport e10086d4a75091fefe16fbd365e8e576e9912bd5 from #3770{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title '[release/v1.9] docs(examples): Add documentation for `examples/tracing/golang-push`' --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-3770-to-release/v1.9

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

# Remove the local backport branch
git switch main
git branch -D backport-3770-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-3770-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 e10086d4a75091fefe16fbd365e8e576e9912bd5

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-3770-to-release/v1.10
# Create the PR body template
PR_BODY=$(gh pr view 3770 --json body --template 'Backport e10086d4a75091fefe16fbd365e8e576e9912bd5 from #3770{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title '[release/v1.10] docs(examples): Add documentation for `examples/tracing/golang-push`' --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-3770-to-release/v1.10

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

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