Perform deploy-time component analysis

[tleguijt]

We clone the repo of each component when performing a mach update. If we implement the same behaviour during a mach generate there are a couple advantages that it brings:

• We can detect other files or directories that might be useful for a MACH deployment for example a dashboard directory to manage a Azure Dashboard or example-data directory to automatically load example data
• Read out a .mach configuration file to avoid having to set certain settings in the MACH configuration; for example the has_public_api, integrations and all that. It also makes it easier to upgrade to newer versions when, for example the set of integrations changes over time.

Things we might consider:

• Document how to cache the .mach directory in the CI/CD sections of the documentation
• See if we can avoid Terraform having to clone the same repositories again