Add PM diagnostics to the new UKCA Diagnostics Handling system.

[mo-pmol]

This issues continues the development started in Trac/FCM UKCA:#216 .

This issue covers the changes required to expand the number of diagnostics covered by the new diagnostic handling mechanism added in UKCA:#29 required by the NUAQ configuration.

Linked UM ticket: UM:7526 TO BE MIGRATED TO GITHUB

Latest Trac/FCM branch to be migrated to GitHub: r7497_github_migration_nuaq_pckg opened from the head of the fcm/trac UKCA repository trunk at ukca.x/trunk@7497

The table below list all the diagnostics migrated to the new UKCA diagnostics handling system.

Diagname	Stashcode
pm10_wet	38560
pm2p5_wet	38561
pm10_dry	38562
pm2p5_dry	38563
pm10_so4	38564
pm2p5_so4	38565
pm10_bc	38566
pm2p5_bc	38567
pm10_oc	38568
pm2p5_oc	38569
pm10_ss	38570
pm2p5_ss	38571
pm10_du	38572
pm2p5_du	38573
pm10_nh4	38669
pm2p5_nh4	38670
pm10_no3	38671
pm2p5_no3	38672
pm10_nn	38673
pm2p5_nn	38674

[mo-pmol]

As this is my first UKCA Github issue related to a change already started on FCM/TRAC I will add some information about how I migrate the code.
All information is available in the working practices site.

1.- Prepare the fcm branch for migration.

1.a) Ideally, open a new branch from the git_migration tag (git_migration = 7497 ). I didn't noticed and opened from the head of the trunk instead, but they are the same. 

1.b) Merge your developer branch into your migration branch

1.c) Solve conflicts if presented.

1.d) Test the migration branch (done under the UKCA column model)

2.- Prepare your GitHub branch for migration

2.a) Fork the repository - using web based GitHub GUI is fine. Make sure you deactivate the option "copy the main branch only" so you will have access to the full project (main + stable) (see managing forks )

2.b) Clone the repository in your local directory. I used the suggested gh CLI by previously following this instructions to setup the tool here gh_authorisation.html https://cli.github.com/manual/.

2.c) Open a new branch in the local copy of your forked repository.
As this branch is intended to included to migrate an older fcm branch I followed the instructions here branch_migration.html#branch-migration and create the branch from the git_migration tag

 `git switch -c pm_diagnostics git_migration`

3.- Sync your fcm branch with my git branch

Following the advice from the manual site in 2.c, I used rsync to copy my branch changes into my git branch

# NOTE: You need the trailing backslash on the fcm source path
rsync -av --delete --exclude=.git --exclude=.svn path/to/fcm/working/copy/ path/to/git/clone

4.- Add changes to the stagged area and commit changes

git add -u
git commit

5. Merge the stable branch into the git branch

git merge origin/stable

6. Push changes to the GitHub remote repository
   git push --set-upstream origin pm_diagnostics

[mo-pmol]

Forked project under my account including the dev branch in https://github.com/mo-pmol/ukca/tree/pm_diagnostics
Also a first approach to use the branch from GitHub under our team UKCA column model can be seen at https://github.com/MetOffice/NUAQ/issues/21
To-Do:

• Adapt fcm_make workflow task in AQUM workflow to extract and compile the UKCA/UM/Jules, etc code.
• Find an alternative to build the code instead of using fcm (if it is already available).
• Try to update the UM related workflow app using a rose macro app (currently, not working?).
• Ask how to use the mirror repository, to avoid complications when running the code under HPC for both, AQEUR and NAME/UKCA.

Note: This branch contains a fix to solve the missing UM dependencies, mainly modifying the used modules to use the alternative UKCA subroutines instead of the UM ones. This probably will need to be reverted, as there is a dedicated ticket to solve this problem (I need clarification).