Fremake yaml integration

[singhd789]

Is your feature request related to a problem? Please describe.

fre make tools also use their own [model].yaml, compile.yaml and platforms.yaml. However, we only want ONE main model yaml. So, we have to integrate the fremake yamls to have one model yaml.

Describe the solution you'd like

• [x] We could to add a compile section in the main yaml that will include information that exists in the fremake model yamls
  • path to platform yaml
  • path to compile yaml
  • release tag
  • reusable variables: INTEL, FMS_includes, mom_includes
• [x] the compile .yaml and platform.yaml should live in the model's repo as well (the the model yaml needs to point to these)
• [x] fre make needs functionality to combine the model yaml and compile yaml (for reusable variable functionality) and parse the information - changes to yamlfre.py (https://github.com/NOAA-GFDL/fre-cli/blob/main/fre/make/gfdlfremake/yamlfre.py)

[singhd789]

@rem1776, here's what you can do: 1) create own branch based off issue 2) create an ESM4_example folder in fre/make/tests 3) put your yamls you've created for fremake in there 4) create a shell of the model yaml already established for ESM4 (https://github.com/NOAA-GFDL/fre-cli/blob/main/fre/pp/tests/example_ppyamls/am5.yaml) 5) I'm thinking add in a compile section under shared, including info in the esm4.yaml you've created 6) add compile section under each experiment (just pointing to the compile yaml) (then that esm4.yaml can eventually be removed)

@singhd789: 1) do the same for the am5 model once I get working yaml updates with that 2) rework parsing in fremake so it can get the right compile info from the new model yaml

Both: 1) test fremake functionality to make sure it's parsing the yamls correctly