bdns: reduce cardinality of histograms

Using the query from https://www.robustperception.io/dropping-metrics-at-scrape-time-with-prometheus: topk(20, count by (__name__, job)({__name__=~".+"})), I found that the histograms in bdns are far and away our highest cardinality metrics.

That's because they are histograms (already high cardinality), and have many labels, and some of the label values have high cardinality (for instance, the resolver).

We should tweak these: for the histogram metrics, we are mostly interested in the time to do various operations, so we should remove almost all labels. We can then put those labels on counter metrics, which inherently have lower cardinality. This will reduce our storage and memory requirements for Prometheus, and will make querying these DNS histograms cheaper.

Start by locating the bdns histogram and counter metric definitions, then review their labels and the Prometheus cardinality query linked in the issue. Done means histogram metrics retain only labels needed for operation timing, while the required labels move to lower-cardinality counters and the resulting metric cardinality is reduced.