Add docs links to document and hover

[radeksimko]

Depends on hashicorp/hcl-lang#8
Depends on hashicorp/terraform-schema#10

---

This adds links to relevant documentation for providers via hover data and documentLink method, which then results in the following UX in VS Code:

Maybe this is not the best UX, but we don't have any control over how clients (such as VS Code) use the documentLink and if at all. Sublime Text for example doesn't implement it at all, so we are left with just hover:

I don't have strong opinion on how we link to docs UX-wise, but I think we could just roll it out and see how people (dis)like it.

Relatedly the UTM parameters will help us identify any click-throughs to the Registry using any of these two features. All URLs have these parameters appended:

• utm_source=terraform-ls
• utm_content - e.g.documentLink or documentHover
• utm_media - e.g. vscode or Sublime Text LSP

[aeschright]

👍

[nfx]

this PR does not allow going to resource documentation, only provider.

[mercuriete]

this only works on provider block
but not in required_providers block:

example:

versions.tf

terraform {
  required_version = ">= 0.14.5, <= 0.14.7"
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "3.29.1"
    }
  }
}

in this example hover is not working.
I think this example is important because lot of users don't declare provider instead they use default parameters and do
required_providers + .terraform.lock.hcl

[radeksimko]

Correct, this is the current limitation we plan to address. I'm sorry for not being clear about it in the PR description.

Feel free to follow #190 for resources, data sources and modules, or #440 for required_providers block.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the context necessary to investigate further.