Don't allow SP, fates, or nofire tests to turn fire_emis on (and make sure our tests don't do this either)

[ekluzek]

When -fire_emis is added to CLM_BLDNML_OPTS it should fail for configurations where fire-emissions won't be passed back. Right now that's SP mode, when nofire is turned on for BGC, or for FATES.

The FORTRAN code and build-namelist should disallow these options.

And we should make sure our testing don't turn on fire-emissions for these configurations.

Related issue: #2759

Definition of done:

• Get the PF unit tests started
• Update submodules so that full ESMF is available
• Finish the unit tests with full ESMF
• Make the needed changes in FORTRAN source and continue to update the unit tests

[ekluzek]

In order to get this to work and have it tested in the FORTRAN code, I need to add unit testing around this. I've started doing that, but found out that for example shr_fire_emis_mod.F90 needs the full ESMF library. This is OK, since work was done to bring this into the unit-testing framework for submodules.

As such I need to work on #2640 before getting back to this.

[ekluzek]

The first part of this for Sprint 11 was a few days of work. I put it at 0.5 of a week.