List of SCREAM log tasks

Currently the amount of information that is printed to one of the logs in a scream run is very minimal. In contrast, EAM prints quite a bit of information. This issue will detail a set of tasks that we may want to implement as we start running CIME based simulations.

- [x] Write SCREAM output to the atm.log file rather than e3sm.log. Currently all SCREAM output uses just `printf` which seems to write to e3sm.log. Given that a lot of information is ATM specific, such as the set of HOMME namelist options used, we will want to create infrastructure to pass the ID of the atm.log file to SCREAM.
- [ ] Print a list of all Field Managed variables complete with short name, long name, units, dimensions
- [ ] Optional - also list if the FM variable is required, computed or both for a SCREAM run.
- [ ] Print the set of ATM processes used for this run, which order, what type of coupling.
- [ ] Print the timestep information. Such as the physics timestep, the start date, if there is any sub cycling.
- [ ] Print if this is an initial run or a restart run.
- [x] Print the HOMME output to atm.log instead of e3sm.log. This is different then the task for scream in general because this task is focuses on passing the appropriate iulog to the homme code so it can handle output.
- [x] Make an option to print the `nstep` and `time` information each step.
- [ ] Goes with the above, in EAM the nstep is accompanied by 3 basic values about global mass and energy. We could do something similar.
- [x] Print the name of the initial condition file (or restart file) used.
- [ ] Print any output information, for example if output is requested, what fields are in it, what frequency of output, what type, and what the name of the file is.