Ensure the analyzer and reporter can handle with action as a unique replace action.

[rafaelherik]

Summary

• Prior to this change, Terraform’s “replace” operations were being folded into generic apply or destroy workflows, resulting in inaccurate counts and reporting.
• This PR updates both the Analyzer and the Reporter so that “replace” is recognized and handled as its own action type throughout the processing pipeline.

What Changed

• Analyzer

  • Added “replace” to the set of supported actions
  • Updated the diff logic so that any plan entry with a “replace” change is categorized correctly

• Reporter

  • Enhanced the output schema to include a “replace” column in both detailed tables and summary sections
  • Adjusted summary statistics to surface replace counts separately from apply/destroy

• Tests

  • New unit tests covering scenarios with replace-only, mixed replace/apply/destroy, and edge cases (e.g. replace followed by no-op)
  • Extended snapshot tests to ensure report templates render the replace column as expected

Why This Matters

• Having a dedicated “replace” category improves visibility into resource lifecycles, especially for workflows that rely on in-place replacement versus full destruction or creation.
• Accurate analytics and reporting empower teams to optimize their change management and catch expensive or risky replacements before they go live.

Backward Compatibility

• No breaking changes: code paths for apply, destroy, and import remain untouched if “replace” never appears in the plan.
• Reporters will simply add an extra column when replace actions are present.