Configuration with pyaro repeats name a lot

[magnusuMET]

The configuration when using pyaro has needlessy many occurences of the same name, as seen in the following configuration for a run using the EEA pyaro-reader.

{
  "obs_cfg": {
    "EEA-unverified": {
      "obs_id": "EEA-unverified",
      "obs_config": {
        "name": "EEA-unverified",
        "data_id": "eeareader",
      },
      "obs_name": "EEA-unverified"
    }
}

We should find a new config setup before pyaro is used in too many places

[lewisblake]

Agreed some clean up would be nice. Here is a short explanation of what things currently mean

{
  "obs_cfg": {
    "EEA-unverified": { # this is user-defined and can be anything you want. shown on webpage if `var_web_interface` not defined
      "obs_id": "EEA-unverified", # this is required by ObsEntry. In vanilla pyaerocom, maps to a obs network defined in paths.ini
      "obs_config": { # pyaro stuff, name matching obs_id might be redundant, probably should talk with Daniel
        "name": "EEA-unverified",
        "data_id": "eeareader", # maybe pyaro_id would be clearer
      },
      "obs_name": "EEA-unverified" # this get created when using a getter on a ObsEntry instance. Either is the var_web.interface name if provided, or it's the key supplied by the user
    }
}