Label filter settings not working as expected

[fitillo]

Describe the bug
Hi, thanks for the wonderful work in this project. Proving really useful! I just think that the feature for filtering out labels is not working as expected or maybe I don't get how to use it properly. I'm setting up labels in the "Label Filter Settings" inside settings scenario, but I get alerts on thresholds for those labels.

To Reproduce
Steps to reproduce the behavior:

1. Create a new scenario inside a project and configure tokens to use jtl_listener_service
2. Run locust for my project. Test run is uploaded properly and can be seen inside JTL
3. Set the last run as base run. Main scenario screen -> test run -> edit -> add mandatory fields and tick on "Set as base run"
4. Configure notification for "Degradation of performance"
5. Run another load test forcing degradation to check results are as expected. All good and notification received. I can even see degradation per label (API) inside a test run which is very nice.
6. Scenario -> settings -> "Label Filter Settings" -> Add labels here I don't want degradation to be considered
7. Run new test run -> Only 1 of these labels marked to be filter out is degraded. I still get the notification and the test run is set as "Performance Regression Detected"

Expected behavior
There shouldn't be a Performance Regression for this run since the only label degraded was in the filter out list.

Screenshots
Here can see the screenshots of the degradation and the configuration:

Additional context
I've tried with both:

• label: index Operator: includes
• label: /users?index=2 Operator: match (one per as many as I have here). I'm guessing this one could have issues due to regexp, but the first option with includes operator should work fine.

Did JtlReporter make you happay in any way?
Really great tool! Initially I was looking into programmatically comparing locust's reports, but this tool provides really great value :)