Stale diagnostics for *.json files

[dbanck]

Context

With support for *.tf.json files (introduced in #498) and support for *.tfvars.json files (introduced in #519), we are now publishing diagnostics for those kinds of files, too.

Expected Behavior

When changing/opening/closing a terraform JSON file, we should publish updated diagnostics to avoid stale diagnostics.

Actual Behavior

Diagnostics for any JSON files (*.tf.json, *.tfvars.json) are only published, when a *.tf is changed/opened/closed in the corresponding module. Fixing an issue inside a JSON file will not trigger an update.

valid JSON file, stale problems

Steps to Reproduce

1. Create an invalid *.tf.json or *.tfvars.json file:

{
  "image_id": "ami-abc123",
  "availability_zone_names": ["us-west-1a", "us-west-1c"]

2. Open a *.tf file in the same module.
3. Fix the error in the JSON file.