Reducing PSyclone complexity within and across code bases - Umbrella Issue

### Are there any linked Issues or Pull Requests?

#672 - Forking psyclone_tools
#703 - PSyTran material to save

### Brief description

PSyclone transformation scripts and related content currently sit across four different spaces within the Met Office:

1. PSyclone - the main PSyclone software from within the [software stack](https://github.com/MetOffice/lfric_core/blob/a4caea11d9984b109fe00d8309a6f135b1cdf59a/documentation/source/getting_started/installation/software_dependencies.rst)
2. LFRic_Apps - [transformation scripts](https://github.com/MetOffice/lfric_apps/tree/main/applications/lfric_atm/optimisation) & [transmute functions](https://github.com/MetOffice/lfric_apps/tree/main/interfaces/build/transmute_psytrans)
3. LFRic_Core - [psyclone_tools](https://github.com/MetOffice/lfric_core/tree/main/infrastructure/build/psyclone)
4. PSyTran - [tools for transformation scripting](https://github.com/MetOffice/PSyTran)

As development of PSyclone and transformation scripts progress, the complexity within these spaces will increase. This Issue acts as an umbrella for all tickets reducing PSyclone's growing complexity across the Met Office code bases.

### Further details of the issue.

An plan for reducing the number of code base's which PSyclone content is currentl found can be viewed here: [First Steps Plan](https://metoffice-my.sharepoint.com/:w:/g/personal/joseph_abram_metoffice_gov_uk/IQB5SEUCbnFuSLzcCvVIC7XEASbr8DXEJzw-v3SlPRZZaKQ?e=En069I)