services/friendbot: Instrument friendbot to emit traces

[satyamz]

PR Checklist

PR Structure

• This PR has reasonably narrow scope (if not, break it down into smaller PRs).
• This PR avoids mixing refactoring changes with feature changes (split into two PRs
  otherwise).
• This PR's title starts with name of package that is most changed in the PR, ex.
  services/friendbot, or all or doc if the changes are broad or impact many
  packages.

Thoroughness

• This PR adds tests for the most critical parts of the new functionality or fixes.
• I've updated any docs (developer docs, .md
  files, etc... affected by this change). Take a look in the docs folder for a given service,
  like this one.

Release planning

• I've reviewed the changes in this PR and if I consider them worthwhile for being mentioned on release notes then I have updated the relevant CHANGELOG.md within the component folder structure. For example, if I changed horizon, then I updated (services/horizon/CHANGELOG.md. I add a new line item describing the change and reference to this PR. If I don't update a CHANGELOG, I acknowledge this PR's change may not be mentioned in future release notes.
• I've decided if this PR requires a new major/minor version according to
  semver, or if it's mainly a patch change. The PR is targeted at the next
  release branch if it's not a patch change.

What

services/friendbot: Instrument friendbot to emit traces. Traces will be sent to Grafana alloy which will send traces to Grafana tempo.

Trace looks like this in Grafana tempo:

Why

• We want to have an ability track request lifecycle
• Help identify performance bottlenecks.

Known limitations

This PR updates several dependencies. We need land this carefully.

Issue:

https://github.com/stellar/ops/issues/4005

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	golang/​github.com/​go-chi/​chi/​v5@​v5.1.0
	golang/​go.opentelemetry.io/​otel@​v1.28.0 ⏵ v1.34.0	+1
	golang/​github.com/​stretchr/​testify@​v1.9.0 ⏵ v1.10.0	+1
	golang/​go.opentelemetry.io/​otel/​sdk@​v1.28.0 ⏵ v1.34.0	+1
	golang/​github.com/​riandyrn/​otelchi@​v0.12.1
	golang/​go.opentelemetry.io/​otel/​trace@​v1.28.0 ⏵ v1.34.0	+1

View full report

[Copilot]

Pull Request Overview

This PR instruments the friendbot service to emit OpenTelemetry traces that will be sent to Grafana Alloy and forwarded to Grafana Tempo for distributed tracing capabilities and performance monitoring.

• Added a new utils/tracer package with OpenTelemetry configuration
• Updated friendbot service to use context-aware tracing throughout the request lifecycle
• Added OpenTelemetry middleware to the HTTP router for automatic request tracing

Reviewed Changes

Copilot reviewed 9 out of 10 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
utils/tracer/tracer.go	New utility package for OpenTelemetry tracer initialization and configuration
services/friendbot/main.go	Updated to initialize tracing, add OpenTelemetry middleware, and use chi/v5 router
services/friendbot/internal/friendbot_handler.go	Added tracing instrumentation to HTTP request handlers
services/friendbot/internal/friendbot.go	Updated Pay method to accept context for tracing
services/friendbot/internal/minion.go	Added context parameter and span instrumentation to minion operations
services/friendbot/internal/minion_test.go	Updated test functions to pass context parameter
services/friendbot/internal/friendbot_test.go	Updated test functions to pass context parameter
services/friendbot/friendbot.cfg	Added otel_endpoint configuration
go.mod	Updated dependencies to include OpenTelemetry packages and chi/v5

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[satyamz]

I am fixing the internal package tests.

[leighmcculloch]

Few comments inline.

[leighmcculloch]

Before merging can you check that this will still function okay with quickstart? You can do that by building quickstart with the friendbot git ref pointing at your friendbot pr commit sha.