Add support for dynamic exclusion filter data

[Anilm3]

This PR introduces support for configurable exclusion filter data, allowing for exclusion filters with a specified matcher but undefined data from the get-go. This allows the update of the matcher without having to reinstantiate all exclusion filters and enables the suspicious attacker blocking features, which relies on a specific denylist.

The configuration key for this new dynamic data is exclusion_data, and the schema is exactly the same as the one used for rules_data, for example:

{
  "exclusion_data":  [
    {
      "id": "usr_data",
      "type": "data_with_expiration",
      "data": [
        {
          "value": "user",
          "expiration": 500
        }
      ]
    }
  ]
}

Related Jira: APPSEC-53545

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 80.70175% with 11 lines in your changes missing coverage. Please review.

Project coverage is 83.68%. Comparing base (4aa0a7a) to head (60ef9b7).

Files	Patch %	Lines
src/ruleset_builder.cpp	69.23%	5 Missing and 3 partials ⚠️
src/parser/data_parser.cpp	84.61%	0 Missing and 2 partials ⚠️
src/rule.hpp	0.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #316      +/-   ##
==========================================
- Coverage   83.70%   83.68%   -0.03%     
==========================================
  Files         137      137              
  Lines        6065     6086      +21     
  Branches     2869     2882      +13     
==========================================
+ Hits         5077     5093      +16     
- Misses        367      369       +2     
- Partials      621      624       +3     

Flag	Coverage Δ
waf_test	83.68% <80.70%> (-0.03%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-07-11 15:26:12

Comparing candidate commit 60ef9b7 in PR branch anilm3/exclusion-data with baseline commit 4aa0a7a in branch master.

Found 3 performance improvements and 0 performance regressions! Performance is the same for 16 metrics, 0 unstable metrics.

scenario:lowercase_transformer.random

• 🟩 execution_time [-72.569µs; -65.436µs] or [-3.971%; -3.580%]

scenario:remove_nulls_transformer.random

• 🟩 execution_time [-2.102ms; -2.090ms] or [-17.124%; -17.021%]

scenario:ruleset_1.10.0.random

• 🟩 execution_time [-9.432ms; -9.297ms] or [-3.419%; -3.370%]