validate rose configs against metadata on installation

[oliver-sanders]

Issue transferred from metomi/rose#1908

On install run validator macros against:

1. The suite config?

• And each optional suite config individually?

2. The app configs?

• And each optional app config individually?

From the copy in:

a. The source dir (pre-install)?

• Can block installation upon encountering invalid configs.
• Cannot validate any apps that are installed using Rose file installation.

b. The run dir (post-install)?

• Can't block installation (because it has already happened).
• Can quibble, log warnings and change the exit status of the install command.

When:

i. By default (with a CLI flag to opt-out)?

• Could make installation slow.

ii. When a CLI flag is used (opt in)?

• Would never be used.

iii. According to the config?

• E.G. Allow the rose-suite.conf to configure apps to exclude?
• E.G. Support the rose macro --no-warn=WARNING_TYPE opt?

Context:

• Validating the suite config should be quick.
• However, the apps may take a while.
• Not all opt configs are necessarily valid in of themselves.
  • Though it can be contested that this is poor design.
  • Note: some opt confs may be designed to be used in combination with others.
• The proportion of real world suites that pass rose macro is likely quite low.