Support Terraform post-plan scanning

[bivas]

Is your feature request related to a problem? Please describe.
When writing resource, some values can be assigned only after Terraform creates a plan.
e.g. Setting transit_encryption_enabled = ${var.transit_encryption_enabled} while the var value is false

resource "aws_elasticache_replication_group" "this" {
  replication_group_description = "desc"
  replication_group_id = "id"
  transit_encryption_enabled = ${var.transit_encryption_enabled}
}

Describe the solution you'd like
Be able to run queries on Terraform plan report

Describe alternatives you've considered
Warn that certain values aren't scannable (like having a var or local instead of actual value)

[rogeriopeixotocx]

@bivas thank you for your input. This is something interesting and if done could also reduce a lot of FP noise. We need to find a smart way to do this without having to rewrite all our terraform queries. The first step would be to analyze the tfplan output JSON structure and compare it with our current internal KICS payload. In this way, we could see if the current queries can be adapted with minimum changes.