Fix providers that depend on output of module

[aliscott]

This fixes the case where a provider block depends on an output of a module and then that provider is passed to the module and used in a data resource.

Before this would create a circular dependency in the graph evaluator because we were treating providers passed into modules as an edge in the graph. Instead now we just maintain a reference to providers when a module is created and then evaluate them and add them to the context at various points in the evaluation process:

1. Before we evaluate a data block, since for special data attributes we might need the provider on the context (e.g. aws_current_region)
2. When we are closing out the module, since after this we collect the default tags values from the module to add to any of the resources.

We could improve this in two ways, but this would be a bigger refactor at the moment:

1. Maintaining a global context for the evaluated providers, instead of adding them to each modules evaluation context.
2. Only evaluating the provider blocks if we need to, instead of for all data resources.