#12222 - Add redirects for ABP installation links

hiera/roles/web/redirect/eyeo.yaml

Index: hiera/roles/web/redirect/eyeo.yaml
===================================================================
--- a/hiera/roles/web/redirect/eyeo.yaml
+++ b/hiera/roles/web/redirect/eyeo.yaml
@@ -60,3 +60,8 @@
   adblockplus/acceptable_ads_opt_out: "https://adblockplus.org/acceptable-ads#optout?"
   adblockplus/terms: "https://adblockplus.org/terms"
   adblockplus/eyeo: "https://eyeo.com/?"
+  adblockplus/opera_install: "https://addons.opera.com/extensions/details/opera-adblock/"
+  adblockplus/ie_install: "https://update.adblockplus.org/latest/adblockplusie.exe"
+  adblockplus/safari_install: "https://update.adblockplus.org/latest/adblockplussafari.safariextz"
+  adblockplus/ios_install: "https://itunes.apple.com/us/app/adblock-plus-abp-remove-ads-browse-faster-without-tracking/id1028871868?mt=8"
+  adblockplus/edge_install: "https://www.microsoft.com/store/p/adblock-plus/9nblggh4r9nz"

[mathias, 2018/06/13 17:52:00]

Please add `?` signs to the end of the target links, e.g. `foo:
https://example.com/bar?`, otherwise any incoming query parameters (GET) will
get included with the redirect.

This is something I just re-learned recently, though we've discovered and worked
around it the same way before. See i.e. `adblockplus/eyeo` above. Also please
note that I do not know how to prevent this from happening when the target link
includes GET parameters itself (some of the new ones here do as well). IIRC one
can write something like `foo: bar?baz=1?` to achieve the sane, though you would
need to test that upfront.

[f.lopez, 2018/06/13 19:16:27]

Your recall is correct, after the last ? the parameters won't be included in the
redirect, I'll add a follow up codereview for this since I already pushed this
change