[Enhancement]: Explore collection of additional v3 EAMxx metadata

### Is your feature request related to a problem?

In a recent meeting, there was a discussion about how v3 EAMxx includes additional metadata that is not captured in our currently workflows (e.g., PACE).

### Describe the solution you'd like

We need:

1. Figure out the additional metadata we want to store
2. Figure out the method of collecting this metadata and where to store it (e.g., PACE, SimBoard)
3. Where/how we want to display these fields on SimBoard

### Describe alternatives you've considered

_No response_

### Additional context

Notes from 10/7/25 meeting:
* yaml file structure, namelist – PACE handle this automatically? Or offload to SimBoard
* OMEGA use similar format
* scream only is C++ code