Backport of Validate passing default providers through modules into v0.15

[teamterraform]

Backport

This PR is auto-generated from #28606 to be assessed for backporting due to the inclusion of the label 0.15-backport.

The below text is copied from the body of the original PR.

---

Add validation for the local side of the providers map assignments in module calls. If these did not actually correspond to a configuration during runtime, the user would be presented with a missing provider error with the assumed address of the provider, but no indication how to configure that address. We can detect these during validation, and present a much more precise error

╷
│ Warning: No configuration passed in for provider aws in module.mod1
│
│   on mod1/main.tf line 15, in module "mod2":
│   15:     aws.local = aws
│
│ Provider aws is referenced within module.mod1, but no configuration has been supplied.
│ Add a provider named aws to the providers map for module.mod1 in the root module.

It was also assumed that inherited providers could be referenced within modules, which is understandable because resources effectively do the same. This inheritance does not work in module calls however, because the provider is looked up in the next child module, one level removed from the inherited provider. Rather than re-work inheritance to account for this edge case, we can direct users to create a more explicit configuration by declaring the name within the module, so that we can follow up with the above recommendation if no configuration is presented.

│ Warning: Provider aws is undefined
│
│   on mod1/main.tf line 15, in module "mod2":
│   15:     aws.local = aws
│
│ No provider named aws has been declared in module.mod1.
│ If you wish to refer to the aws provider within the module, add a provider configuration, 
│ or an entry in the required_providers block.

Fixes #28565

[github-actions]

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