Draft: redirects: Support redirect backed by a map

We need a lot of redirect for bugs.al.org->GitLab (there is over 70k tasks) and using a map is simple and efficient.

Ref #320 (closed)

TODO:

• Does it even work?
• How well does it performs with 70k redirects?
• How do we handle the certificate pre-bugs.al.org shutdown?

roles/redirects/defaults/main.yml

 # Every entry creates a redirect listening on port 80 and 443 with the following parameters:
 #   - domain: the domain to listen on
 #   - to: the redirect target as defined by the nginx return statement
-#   - type: HTTP status code to use (302 = temporary redirect, 301 = permanent redirect)
+#   - type: (simple, map)
+#   - http_code: HTTP status code to use (302 = temporary redirect, 301 = permanent redirect)
 redirects:
   - mailman:
     domain: mailman.archlinux.org
     to: https://lists.archlinux.org$request_uri
-    type: 301
+    http_code: 301
   - static.conf:
     domain: static.conf.archlinux.org
     to: https://gitlab.archlinux.org/archlinux/conf-files/-/raw/master$request_uri
-    type: 302
+    http_code: 302
+  - bugs:
+    domain: bugs.archlinux.org
+    to: gitlab.archlinux.org
+    type: map
+    http_code: 302