Incorrect Handling of [delete, create] Replacement Actions

[rafaelherik]

Currently, when the analyzer and reporter encounter a [delete, create] action (which typically indicates a resource replacement), they treat it as two independent operations. This leads to confusion, as the connection between the deletion and creation of the same resource is lost in the output.

Expected Behavior

• The [delete, create] pair should be recognized and reported as a single replacement operation.
• The reporter should highlight the attribute(s) that triggered the replacement, if available (e.g., changes to immutable fields).

Goal

Improve the clarity of plan outputs by:

• Linking the delete and create actions as a replacement.
• Identifying and displaying the specific attribute(s) responsible for the replacement.

This will make it easier to understand why a resource is being replaced and improve the overall usefulness of the plan report.