[CWS] Reset rule disarmers only after a new ruleset is loaded

[YoannGh]

What does this PR do?

This makes sure rule disarmers are reset only after the rule engine starts evaluating a new ruleset.
Prior to this change, rule disarmers were reset before the old and new rulesets were swapped, causing the actions of old rules to be performed again for a short period of time.

Motivation

Describe how to test/QA your changes

Possible Drawbacks / Trade-offs

Additional Notes

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Run ID: 77dc659e-f4e2-41b8-8c2e-bcdbd8879b5e Metrics dashboard Target profiles

Baseline: 8802a20
Comparison: d71d89a

Performance changes are noted in the perf column of each table:

• ✅ = significantly better comparison variant performance
• ❌ = significantly worse comparison variant performance
• ➖ = no significant change in performance

No significant changes in experiment optimization goals

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	pycheck_lots_of_tags	% cpu utilization	+1.36	[-1.06, +3.77]	1	Logs
➖	idle	memory utilization	+0.72	[+0.67, +0.76]	1	Logs
➖	idle_all_features	memory utilization	+0.46	[+0.36, +0.55]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	+0.35	[-0.14, +0.85]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	+0.20	[+0.14, +0.27]	1	Logs
➖	file_to_blackhole_300ms_latency	egress throughput	+0.07	[-0.11, +0.25]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	+0.01	[-0.21, +0.23]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.02, +0.02]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	-0.01	[-0.34, +0.32]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	-0.02	[-0.09, +0.05]	1	Logs
➖	file_tree	memory utilization	-0.08	[-0.19, +0.03]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	-0.15	[-0.39, +0.10]	1	Logs
➖	otel_to_otel_logs	ingress throughput	-0.72	[-1.52, +0.09]	1	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-1.92	[-2.64, -1.20]	1	Logs
➖	basic_py_check	% cpu utilization	-2.44	[-4.99, +0.12]	1	Logs

Bounds Checks

perf	experiment	bounds_check_name	replicates_passed
✅	file_to_blackhole_0ms_latency	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency	memory_usage	10/10
✅	file_to_blackhole_100ms_latency	memory_usage	10/10
✅	file_to_blackhole_300ms_latency	memory_usage	10/10
✅	file_to_blackhole_500ms_latency	memory_usage	10/10
✅	idle	memory_usage	10/10

Explanation

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

3. Its configuration does not mark it "erratic".