Allow `Replace_triggered_by` to Refer to Module or Module Resource
Fleeting- External reference: https://github.com/hashicorp/terraform/issues/31713
recommended way to trigger something based on a change in a separate module is to route the desired outputs into a managed resource which can be monitored for changes. Currently the most convent resource for this is a null_resource
we can close this with the adoption of terraform_data