Add logic for IP-based dynamic redirects

[acelaya]

Closes #2120

Allow redirect rule conditions based on visitors IP addresses. Condition values can be static IP addresses (100.200.80.40), CIDR blocks (192.168.10.0/24) or wildcard patterns (11.22.*.*).

Alternative implementation to #2121, with the next differences:

• The logic to check if the IP address matches the rule pattern, is shared with the existing logic to check if current IP address matches the values provided in DISABLE_TRACKING_FROM.
• Every condition will allow only one Ip address to match, instead of a comma-separated list. If more than one group should redirect to the same place, users will simply have to create a few consecutive rules.
• Validation is done in RedirectRulesInputFilter.

TODO

• API test.
• IP address/CIDR block/Wildcard pattern validation.
• API spec.

[acelaya]

All this logic was originally defined in RequestTracker, and has been extracted to be reused for IP-based redirect rules.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.98%. Comparing base (e4f66b7) to head (9e6cdcb).
Report is 1 commits behind head on develop.

Additional details and impacted files

@@              Coverage Diff              @@
##             develop    #2151      +/-   ##
=============================================
+ Coverage      95.95%   95.98%   +0.03%     
- Complexity      1507     1520      +13     
=============================================
  Files            264      266       +2     
  Lines           5116     5137      +21     
=============================================
+ Hits            4909     4931      +22     
+ Misses           207      206       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.