[fix] Fix incorrect usage of iter package in aggregator (jaegertracin…

…g#6403)

## Description of the changes
- jaegertracing#6401 was accidentally
using the official `iter` package instead of the internal one. This PR
fixes that usage.
- Added a linter rule so we don't accidentally use the official package
again until we upgrade to Go 1.23

## How was this change tested?
- CI

## Checklist
- [x] I have read
https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
- [x] I have signed all commits
- [x] I have added unit tests for the new functionality
- [x] I have run lint and test steps successfully
  - for `jaeger`: `make lint test`
  - for `jaeger-ui`: `npm run lint` and `npm run test`

---------

Signed-off-by: Mahad Zaryab <mahadzaryab1@gmail.com>

.golangci.yml

@@ -146,6 +146,14 @@ linters-settings:
         files:
           - "!**/jptrace/**"
 
+      # TODO: remove once we have upgraded to Go 1.23
+      disallow-iter:
+        deny:
+         - pkg: iter
+           desc: "Use github.com/jaegertracing/jaeger/pkg/iter"
+        files:
+          - "**"
+
   goimports:
     local-prefixes: github.com/jaegertracing/jaeger
   gosec:

internal/jptrace/aggregator.go

@@ -4,10 +4,10 @@
 package jptrace
 
 import (
-	"iter"
-
 	"go.opentelemetry.io/collector/pdata/pcommon"
 	"go.opentelemetry.io/collector/pdata/ptrace"
+
+	"github.com/jaegertracing/jaeger/pkg/iter"
 )
 
 // AggregateTraces aggregates a sequence of trace batches into individual traces.