Add `rose macro -V` command to `rtw-tests.yml` Github Workflow

[chrisbillowsMO]

Description

• Closes #3632

• Link to documentation: N/A

• • *

Before you get started

• [x] ☝ Create an issue to discuss what you are going to do

Checklist

It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

• [x] 🛠 This pull request has a descriptive title
• [x] 🛠 Code is written according to the code quality guidelines
• [x] 🛠 Tests run successfully

---

To help with the number of pull requests:

• 🙏 We kindly ask you to review two other open pull requests in this repository

If you need help with any of the items on the checklists above, please do not hesitate to ask by commenting in the issue or pull request.

[alistairsellar]

@alistairsellar do you remember the conversation we had with Oliver about potentially grouping options via namelists? I'm wondering whether it's worth doing this for the options that we must duplicate in the rose-suite.conf file (because they are defined in e.g. opt conf files) so we can separate them under a "users must not edit these options as they are defined in opt conf files" list? 🤔

Yes, that seems sensible. That list could be called something like "site-specific settings, do not edit".

[ehogan]

@alistairsellar do you remember the conversation we had with Oliver about potentially grouping options via namelists? I'm wondering whether it's worth doing this for the options that we must duplicate in the rose-suite.conf file (because they are defined in e.g. opt conf files) so we can separate them under a "users must not edit these options as they are defined in opt conf files" list? 🤔

Yes, that seems sensible. That list could be called something like "site-specific settings, do not edit".

Great! 👍 @chrisbillowsMO, I will leave it up to you whether you would like to do the above work; if not, would it be possible for you to open a new issue (and assign it to me), please? 😊

[chrisbillowsMO]

@alistairsellar do you remember the conversation we had with Oliver about potentially grouping options via namelists? I'm wondering whether it's worth doing this for the options that we must duplicate in the rose-suite.conf file (because they are defined in e.g. opt conf files) so we can separate them under a "users must not edit these options as they are defined in opt conf files" list? 🤔

Yes, that seems sensible. That list could be called something like "site-specific settings, do not edit".

Great! 👍 @chrisbillowsMO, I will leave it up to you whether you would like to do the above work; if not, would it be possible for you to open a new issue (and assign it to me), please? 😊

Alas no time! 😭 I've raised it as a new issue here: #3679