Preload all config/secrets for a module during its deployment

[alecthomas]

We need to treat all resources, including passwords, as dependencies when deploying the module, and block the deploy until they're all available.

[matt2e]

From other dupe'd issue:

• Write up design doc first
• Want a way to make sure all resources are provisioned & valid before reserving a runner and deploying a module
• At first it will just be to make sure a module context can be created (no missing configs, secrets, dsns)
• Later it will be used for provisioning dbs, generating DSNs, migrating

[matt2e]

Taking myself off this for now. The plan was to work on this with the 1Password / secrets epic, but other things have become higher priority. Putting it back in triage