fix: avoid semantic token modifier inheritance for dependent bodies

[radeksimko]

Fixes #108

UX

Nested dependent blocks no longer inherit the top level modifiers.

Before

After

The examples used a custom VS Code theme:

{
  "name": "Example Theme",
  "semanticHighlighting": true,
  "semanticTokenColors": {
    "hcl-blockType.terraform-resource": {"fontStyle": "bold", "foreground": "#fff"},
    "hcl-blockType.terraform-data": {"fontStyle": "bold", "foreground": "#fff"},
    "hcl-blockType.terraform-module": {"fontStyle": "bold", "foreground": "#3d5aff"},
    "hcl-blockLabel.terraform-module.terraform-name": {"foreground": "#bac4ff"},
    "hcl-blockLabel.terraform-type": {"foreground": "#844FBA", "fontStyle": "bold"},
    "hcl-blockLabel.terraform-resource.terraform-name": {"foreground": "#a589b3"}
  }
}

[dbanck]

LGTM for dependent blocks (os_disk)!

How to we want to highlight "normal" nested blocks inside a body? For example, lifecycle:

[radeksimko]

How to we want to highlight "normal" nested blocks inside a body?

Frankly I don't know yet. My plan was to land it like this and then solicit feedback from theme authors. One direction would be the one described already in hashicorp/terraform-ls#835 - i.e. Core vs Provider blocks

#110 should give us some more flexibility downstream in terraform-schema and react to various needs.