Previously, there was one `aleph_collections` metric with a `category` label. In addition to collection counts by category, we also want to track collection counts by country and languages. In order to keep metric cardinalities under control, I've decided to split the `aleph_collections` metric into three separate metrics: `aleph_collection_categories`, `aleph_collection_countries`, and `aleph_collection_languages`.

Each of these metrics has one additional label `type` which can be either `dataset` or `casefile`. This allows to query for the datasets or investigations in a particular language or related to a particular country.

I have also removed the `category` label from the `aleph_collection_users` metric as it wasn't that useful.

This allows us to get a better understanding of API requests that originate from the UI and requests from third parties using an API key.

This test started to fail with an upgrade of the `phonenumbers` package (imported via `followthemoney`) which included updated phone number validation rules. As a result, the phone numbers in this test case didn’t pass validation anymore and were cleaned from the entites created.

At first glance these numbers seemed to be valid German mobile phone numbers and I was worried that there might be a regression in `phonenumbers`. But according to the International Telecommunication Union, a phone number with the prefix `176` has to be 11 digits long. I adjusted the tests accordingly.

https://www.itu.int/oth/T0202000051/en