🛠️ Make Hutch configuration guidance for installation clearer

[beforan]

Summary

There are three parts to this:

1. What is the clearest way we can document the required Hutch configuration depending on your chosen environment setup
   • e.g. What config do you need based on what prerequisite external components you're using
   • TRE-Controller needs X, MinIO needs Y, etc... but they're all optional
2. Modifying the Ansible Service description should not be a preferred way to apply environment configuration, even when environment variables are used
   • There's no value to specifying the configuration before install time - in fact it puts more pressure on the prerequisite decisions and setup and implies they're more concrete than they actually are
   • It means changing config later is harder or more confusing as a person installing needs to know 2 config methods: one for Ansible and one for environment variables
   • it prevents the ability to use other config sources such as appsettings, if desirable.
3. Documenting how you should do configuration (e.g. appsettings or env vars) and change it later, if Ansible isn't how.

Tasks

• Remove environment configuration from Ansible Service Description for Hutch Agent
• Update documentation to more clearly specify what config needs setting per given prerequisite components
• Update documentation to more clearly explain how to set configuration initially and change it later

Acceptance Criteria

• Ansible doesn't perform Hutch configuration
• Documentation explains configuration approach when installing