Update the field_table yaml format

[uramirez8707]

Is your feature request related to a problem? Please describe.
The current version of the field table yaml is this:

field_table:
- field_type: tracer
  modlist:
  - model_type: atmos_mod
    varlist:
    - variable: sphum
      longname: specific humidity
      units: kg/kg
      profile_type: fixed
      subparams:
      - surface_value: 3.0e-06
    - variable: soa
      longname: SOA tracer
      units: mmr
      convection: all
      chem_param: aerosol
      subparams:
      - frac_pm1: 0.89
        frac_pm25: 0.96
        frac_pm10: 1.0
      profile_type: fixed
      subparams:
      - surface_value: 1.0e-32

The problem with this is that it is not very clear for looking at the table that surface_value is a subparams of profile_type or that frac_pm1, frac_pm25, and frac_pm10 are subparams of chem_param.

It is also not possible to add a schema with this format.

Thus we will like the table to be updated to

field_table:
- field_type: tracer
  modlist:
  - model_type: atmos_mod
    varlist:
    - variable: sphum
      longname: specific humidity
      units: kg/kg
      profile_type:
      - value: fixed
        surface_value: 3.0e-06
    - variable: soa
      longname: SOA tracer
      units: mmr
      convection: all
      chem_param:
      - value: aerosol
        frac_pm1: 0.89
        frac_pm25: 0.96
        frac_pm10: 1.0
      profile_type:
      - value: fixed
        surface_value: 1.0e-32

Describe the solution you'd like

• the converter should be updated to convert the field table to this new format Bettereliminatesubparams fms_yaml_tools#45 @GFDL-Eric
• The parser needs to be updated to be able to read this format Parser: Add ability to read in generic blocks #1519 @uramirez8707
• The code that reads in the field_table yaml format needs to be updated @J-Lentz
• A schema needs to be added to check that a field table yaml format is valid @J-Lentz

Describe alternatives you've considered
N/A

Additional context
N/A