To ensure the debuggability of our cleaned must-gather, we need to offer the ability to consistently replace the same input with the exact same output. 

Think of replacing the detected IP address 192.168.176.133, which could become 10.11.12.1 everywhere. 

Consistently means in a single invocation in a single folder of a must-gather AND across invocations on the same must-gather input (idempotency). To ensure the same IP always stays the same IP across invocations, we can leverage the reporting from CFE-30, which allows us to read previous results and initialize the replacements accordingly.

The following changes are required:

1. The generated replacement report should include the name of the obfuscator and the configuration parameters in the output report.
2. A new CLI flag should be added which specifies a previously generated report.
3. The application should be modified to read the previous report and pre-populate the replacements maps with the replacements from the report if the obfuscator configuration parameters match.

AC:

• CLI should consistently replace the same input with the same output (eg on the IP obfuscator)
• there should be a simple report (json/yaml) file that can carry this logic
• properly tested logic