fix(rcm): store payloads target files content

[avara1986]

Remote Configuration should be able to store previous products target file content due to ASM needs to update all content/rules, the new once and the previous once.

further more, if a RC target file is disabled, RC should remove all configuration related to this target_file.

(Note: this bug was introduced with the new products in 1.10 so there is no need to backport).

e.g:

Actual behavior:

• Payload1:
  • Product ASM_DD. New target file ASM_DD/file_12. Content: {"exclusions": [rule1]}
  • ASM WAF updates with: {"exclusions": [rule1]}
• Payload2:
  • Product ASM_DD. New target file ASM_DD/file_34. Content: {"exclusions": [rule2]}
  • ASM WAF updates with: {"exclusions": [rule2]}
• Payload3:
  • Product ASM_DD. Disable Target File ASM_DD/file_34. Content: {"exclusions": [rule2]}
  • ASM WAF updates with: {"exclusions": []}

With this PR the new behavior is:

• Payload1:
  • Product ASM_DD. New target file ASM_DD/file_12. Content: {"exclusions": [rule1]}
  • ASM WAF updates with: {"exclusions": [rule1]}
• Payload2:
  • Product ASM_DD. New target file ASM_DD/file_34. Content: {"exclusions": [rule2]}
  • ASM WAF updates with: {"exclusions": [rule1, rule2]}
• Payload3:
  • Product ASM_DD. Disable Target File ASM_DD/file_34. Content: {"exclusions": [rule2]}
  • ASM WAF updates with: {"exclusions": [rule1]}

Affected versions

1.10.rcX

Checklist

• Change(s) are motivated and described in the PR description.
• Testing strategy is described if automated tests are not included in the PR.
• Risk is outlined (performance impact, potential for breakage, maintainability, etc).
• Change is maintainable (easy to change, telemetry, documentation).
• Library release note guidelines are followed.
• Documentation is included (in-code, generated user docs, public corp docs).
• Author is aware of the performance implications of this PR as reported in the benchmarks PR comment.

Reviewer Checklist

• Title is accurate.
• No unnecessary changes are introduced.
• Description motivates each change.
• Avoids breaking API changes unless absolutely necessary.
• Testing strategy adequately addresses listed risk(s).
• Change is maintainable (easy to change, telemetry, documentation).
• Release note makes sense to a user of the library.
• Reviewer is aware of, and discussed the performance implications of this PR as reported in the benchmarks PR comment.

[pr-commenter]

Benchmarks

Comparing candidate commit 9b57b98 in PR branch avara1986/rcm-store-payloads with baseline commit 5755849 in branch 1.x.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 56 cases.

[codecov-commenter]

Codecov Report

Merging #5270 (9b57b98) into 1.x (5755849) will increase coverage by 0.09%.
The diff coverage is 95.67%.

@@            Coverage Diff             @@
##              1.x    #5270      +/-   ##
==========================================
+ Coverage   75.84%   75.93%   +0.09%     
==========================================
  Files         872      872              
  Lines       68572    68871     +299     
==========================================
+ Hits        52007    52296     +289     
- Misses      16565    16575      +10     

Impacted Files	Coverage Δ
ddtrace/appsec/_remoteconfiguration.py	65.95% <78.78%> (-1.11%)	⬇️
ddtrace/internal/remoteconfig/client.py	54.51% <78.94%> (+1.29%)	⬆️
tests/appsec/test_remoteconfiguration.py	100.00% <100.00%> (ø)
.../internal/remoteconfig/test_remoteconfig_client.py	95.98% <100.00%> (+3.35%)	⬆️
...ernal/remoteconfig/test_remoteconfig_client_e2e.py	100.00% <100.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more