[Fix]: Separation of conditionals for selecting radiation in Physics call

[fmalatino]

Description
This PR introduces changes to allow orchestration to parse the Physics object call, without entering into the block regarding radiation.

How Has This Been Tested?
Tested using current CI

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules
• New check tests, if applicable, are included
• Targeted model, if this change was triggered by a model need/shortcoming

[oelbert]

Great, thanks for fixing this Frank

[FlorianDeconinck]

Technical detail here: for orchestration the do_radiation is considered a runtime parameter, subject to change, it will therefore orchestrate through. The self._rterrtmgp on the other end is a None value will trigger a code cull and nothing will be orchestrated in the conditional branch

[oelbert]

Technical detail here: for orchestration the do_radiation is considered a runtime parameter, subject to change, it will therefore orchestrate through. The self._rterrtmgp on the other end is a None value will trigger a code cull and nothing will be orchestrated in the conditional branch

That's correct, do_radiation changes at runtime

[oelbert]

One small change, ideally we'd have the compile-time conditional before the runtime one

[oelbert]

Could we reverse the order of these conditionals so the compile-time one is first?

[oelbert]

One more thing

[oelbert]

This should be outside the if do_radiation condition