Route a small set of safe jobs to the default queue

What does this MR do?

A further step on gitlab-com/gl-infra&447 (closed), specifically gitlab-com/gl-infra/scalability#1072

Currently no sidekiq worker is listening for these named queues on gitlab.com (per the tag name) because they aren't in active use and not listening for them gave us a little CPU headroom on redis-sidekiq.

However with the routing rules approach we can now route them to the "default" queue with no added overhead. This is particularly useful as this is a nice safe operation on production because, as above, the relevant jobs are not in active use, and this also exposes Chaos::SleepWorker for testing purposes.

To be deployed as part of a change issue (TBD)

Author Check-list

Please read the Contributing document and once you do, complete the following:

• Assign to the correct reviewer per the contributing document
• Apply the correct metadata per the contributing document

Reviewer Check-list

• Reviewed the diff jobs to confirm changes are as expected
• No changes shown in the diffs not associated with this MR - This may require a rebase or further investigation

releases/gitlab/values/gprd.yaml.gotmpl

@@ -355,7 +355,7 @@ global:
         - ["feature_category=database&urgency=throttled", null] # database-throttled
         - ["feature_category=gitaly&urgency=throttled", null] # gitaly-throttled
         - ["tags=exclude_from_kubernetes", null] # catchall on VMs
-        - ["tags=exclude_from_gitlab_com", null] # special case for testing (only runs actively on staging; includes geo jobs)
+        - ["tags=exclude_from_gitlab_com", default] # special case for testing (only runs actively on staging; includes geo jobs)
         - ["*", null] # catchall on k8s
 
   email: