SCREAM provenance

Two sub-issues:

1. Inputs:
We need to catalog any new input files (namelists, yaml etc.) that SCREAM uses to setup a run.
This list needs to be propagated to CIME so that provenance capture logic knows about the new files to capture.

2. atmchange:
On a related note, the file "replay.sh" captures all the CIME commands that are used to setup and run a case from a specific case directory (create_newcase, case.setup, xmlchange, case.build etc.). This file then gets archived. Example from an E3SM case: https://pace.ornl.gov/replaysh/108415
We need to think if we want to capture atmchange commands to that file or capture them another way to aid reproducibility.