Tripped up by `class` arguments?

An experiment script to build the `io_dev` LFRic application (attached) is having trouble compiling `iterative_solver_mod` due to not being able to find `abstract_linear_operator_type` and `abstract_preconditioner_type` despite both module files having been created.

Is this due to arguments declared as `class` rather than `type`?

[io_dev_app.py.txt](https://github.com/metomi/fab/files/10684709/io_dev_app.py.txt)

This may be related to the Intel compiler. It seems to work with GCC but we need to understand why. Same issue was observed with Gung Ho script.

Start with the attached io_dev_app.py.txt and the build of iterative_solver_mod, focusing on iterative_solver_mod and the abstract_linear_operator_type and abstract_preconditioner_type modules. Compare the Intel and GCC behavior, then check whether the same failure appears in the Gung Ho script. Done means identifying why the module types are not found and documenting or correcting the affected build behavior.

Written by the indexing model from the issue text.