Update latest tracing benchmark SLOs

[sarahchen6]

What Does This Do

Update latest macrobenchmark benchmark failure thresholds based on automatically generated SLOs. Exact changes include:

• normal_operation/only-tracing:
  • tighten agg_http_req_duration_p50 by 3.5%
  • tighten agg_http_req_duration_p99 by 1.7%
• normal_operation/otel-latest:
  • tighten agg_http_req_duration_p50 by 3.5%
  • loosen agg_http_req_duration_p99 by 4.8%
• high_load/only-tracing:
  • loosen throughput by 5.2%
• high_load/otel-latest:
  • loosen throughput by 3.2%

Motivation

The benchmarks are stable according to the APM SDKs Perf SLOs dashboard, but they have been emitting warnings for the past few weeks. Loosen the threshold with T=15% to avoid these noisy warnings while still maintaining a strict bound. The values were auto-generated based on the latest runs of master, so even with the increase of T from 10 to 15%, some thresholds tightened.

Additional Notes

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors

Jira ticket: [PROJ-IDENT]

Note: Once your PR is ready to merge, add it to the merge queue by commenting /merge. /merge -c cancels the queue request. /merge -f --reason "reason" skips all merge queue checks; please use this judiciously, as some checks do not run at the PR-level. For more information, see this doc.