NUOPC and MCT drivers should not use FMS directly

[Hallberg-NOAA]

Throughout the MOM6 code, we have tried to route all calls to FMS routines via routines in the config/src/infra/ directories, in most cases going first through interfaces in the src/framework directory. This includes the code in config_src/drivers/FMS_cap and in
config_src/drivers/solo_driver. However, there are several module use statements in the code in config_src/drivers/mct_cap and config_src/drivers/nuopc cap that are instead using FMS code directly.

Calling FMS via MOM6 wrappers allows us to document and extend the interfaces as used by MOM6 (and SIS2), and it is essential for preserving backward compatibility with older versions of FMS and with gracefully allowing the transitions to newer versions of FMS while minimizing the disruption to MOM6 users.

The MCT_cap and NUOPC_cap driver code should be modified to use the MOM6 wrappers for all calls to use FMS routines, similarly to what was already done in the FMS_cap driver code. Doing so should not change any answers, and it should not substantially alter the run-time, but it will allow for the graceful use of newer versions of FMS and prevent disruptions from using interfaces that are being dropped from FMS.