we'll need some release notes about the breaking change as well

It looks like we won't be able to see references in a case like this:

resource "aws_instance" "example" {
  launch_template {
    id = aws_launch_template.example.id
  }
}

resource "aws_launch_template" "example" {
  name = "example"
  metadata_options {
    http_endpoint = "enabled"
    http_tokens = "required"
  }
}

Where the use case is using a traverse filter to see if an instance has IMDSv2 enforced via metadata_options.http_tokens == 'required' on its associated launch template.

For what it's worth, we don't catch this as a reference on main either. But I bring it up here because if the issue is that we're not seeing or tracking references that come from nested blocks inside resources, I don't know if that has any impact on how to approach this PR.