Fix account attribute to diagnostics metrics

[daniyelnnr]

What is the purpose of this pull request?

This PR adds account information to all diagnostics metrics (logs, HTTP handlers, GraphQL resolvers, and HTTP client operations) to enable filtering, aggregation, and analysis by account. This aligns metrics with the existing logging pattern where account context is already included.

The changes include:

• Adding account_name attribute to request-level metrics (otelRequestMetricsMiddleware)
• Including account in HTTP handler timing and request metrics
• Adding account to HTTP server request lifecycle metrics (total, closed, aborted)
• Including account in GraphQL field resolver metrics
• Propagating account via x-vtex-account header in HttpClient requests
• Extracting account from headers in HttpClient metrics middleware
• Fixing workspace type attribute to use semantic values ('production'/'development')

What problem is this solving?

Currently, diagnostics metrics lack account context, making it difficult to:

• Filter metrics by specific accounts for troubleshooting
• Identify which accounts are experiencing issues or high load
• Aggregate metrics per account for usage analysis
• Correlate metrics with logs (which already include account info)

This creates a gap in observability where metrics cannot be easily attributed to specific accounts, requiring manual correlation or additional queries to understand account-specific behavior.

How should this be manually tested?

1. Deploy the changes to a test environment
2. Make requests to various endpoints (HTTP, GraphQL) from different accounts
3. Query the diagnostics metrics backend and verify:
   • All metrics include the vtex.account.name attribute
   • Account values match the requesting account from context
   • HttpClient metrics show account from propagated headers
   • Fallback to 'unknown' or 'unknown_account' works when context is unavailable
4. Verify metrics can be filtered and aggregated by account
5. Confirm no breaking changes to existing metric names or structures

Screenshots or example usage

Example metric with account attribute:

http_handler_requests_total{
vtex.account.name="mystore",
component="http-handler",
route_id="my-route",
status_code="200"
}

Example query filtering by account:

sum(rate(http_handler_requests_total{vtex.account.name="mystore"}[5m]))

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Requires change to documentation, which has been updated accordingly.

[silvadenisaraujo]

LGTM 🔥