Bound Concurrency of Pod Scraping (Probably with a Work Pool)

## Describe the feature

We've discussed this a few times in slack but it seems worth having an issue for it and I didn't spot one, so here one is :).

As of right now we spawn pod scrapes in parallel for ~every revision with no real bound on the amount we'll attempt at once across revisions. This means we can potentially have an extremely large number of active outgoing scrapes, causing more contention than needed, exceeding keep-alive connection pool size and buffer pools etc. In our larger environments, we see large numbers of connections waiting on DNS and GC when revisions*pods gets large.

We should probably introduce some sort of work pool for the scrapers.

No file or test path is provided. Start by locating the pod-scraping entry point and tracing how scrapes are launched across revisions; determine where concurrency is currently unbounded. Done means concurrent outgoing scrapes are bounded across revisions, with behavior and limits covered by appropriate tests.

Written by the indexing model from the issue text.