Aggregate traces based on controller (or controller-action) rather than the requests path

Operations in Jaeger are currently derived from the request path. This results in an operation being created for every single path. In gstg, for gitlab-workhorse, we've already exceeded 10k operations. This won't scale in production where we will have many more unique requests paths.

We should find a better way of aggregating traces, e.g. based on the controller but it could be any that we find suitable for this, and reconfigure the necessary components. Ideally before we roll out to production.