Add "unit-test like" coverage to Configure operations

[hasheddan]

What problem are you facing?

Provider Name: All
Provider Version: All

Resources are currently configured using a Configure hook, which dictates behavior for operations such as late initialization and publishing connection secrets. Currently, this behavior is only exercised via e2e testing, which does not validate that all permutations of the resource in question will work.

How could Official Providers help solve your problem?

Adding unit test coverage to these hooks is a non-trivial operation because they are mostly dependent on what the underlying TF provider hands back at runtime. However, it may be possible to hook into the TF provider tests (example) to do some preliminary validation that fields we depend on are actually expected to be available at runtime. This would not be a comprehensive solution, but it could go a long way towards eliminating small bugs related to unstructured field references.