Ben EddyandGitHub 6eb213b779 Use a concrete type for metrics.Tag (#8384) ...

## What changed?

Changes `metrics.Tag` from an interface to a concrete type. 

## Why?

To reduce allocations and GC pressure. Tags are often created in hot
paths as part of metrics instrumentation, and interface boxing can
trigger heap allocations.

Here's a benchmark for `metrics.OperationTag("test")`
```
BenchmarkTags-14    	1000000000	       0.3070 ns/op	       0 B/op	       0 allocs/op
BenchmarkTags-14    	69621046	        17.08 ns/op	      32 B/op	       1 allocs/op
```

## How did you test it?
- [x] built
- [x] run locally and tested manually
- [x] covered by existing tests
- [ ] added new unit test(s)
- [ ] added new functional test(s)

2025-10-07 09:50:06 -07:00

..

capture_handler.go

Use a concrete type for metrics.Tag (#8384)

2025-10-07 09:50:06 -07:00

metricstest_test.go

Remove license header from every file (#7689)

2025-05-01 18:50:21 -07:00

metricstest.go

Use a concrete type for metrics.Tag (#8384)

2025-10-07 09:50:06 -07:00

task_queues_test.go

Remove license header from every file (#7689)

2025-05-01 18:50:21 -07:00