WCST_Import axes metadata and band metadata should be added implicitly when global metadata is "auto" in netCDF recipe

[Bang Pham Huu]

For netCDF recipe, axes metadata needs to be specified manually in ingredient file to be available in coverage's global metadata with this configuration, e.g:

	  "axes": {
		"Long": "${netcdf:variable:lon:metadata}",
		"Lat": "${netcdf:variable:lat:metadata}",
	   }

The problem is because there are multiple variables in netCDF (e.g: lon, lat,…) so it cannot be matched automatically to coverage's axes (Long, Lat,…).

However, it could try to parse the variable names which are configured by users from "min" and "max", e.g:

 Here axis variable "lat" is matched to "Lat" CRS axis.

 "Lat": {
              "min": "${netcdf:variable:lat:min}",
              "max": "${netcdf:variable:lat:max}",
               ...
}

Therefore, in ingredient file, with

"metadata": {
    "global": "auto"
 }

Bands and axes variables's metdata specified in the ingredient file will be collected to coverage's metadata to be used later when encoding with netCDF format.