feat: sync-ing collections

[gadomski]

Description

Sync collections from the Open Planetary Computer to this repo.

Here's the printout of collections that don't have config.json files:

These collections are missing config.json files: daymet-annual-pr, daymet-daily-hi, fia, gridmet, daymet-annual-na, daymet-monthly-na, daymet-annual-hi, daymet-monthly-hi, daymet-monthly-pr, gnatsgo-tables, hgb, terraclimate, nasa-nex-gddp-cmip6, gpm-imerg-hhr, gnatsgo-rasters, goes-cmi, conus404, mtbs, noaa-c-cap, 3dep-lidar-copc, alos-fnf-mosaic, mobi, era5-pds, chloris-biomass, kaza-hydroforecast, planet-nicfi-analytic, daymet-daily-pr, gap, planet-nicfi-visual, gbif, alos-dem, alos-palsar-mosaic, deltares-water-availability, us-census, jrc-gsw, deltares-floods, hrea, daymet-daily-na, nrcan-landcover, ecmwf-forecast, nasadem, drcog-lulc, eclipse, esa-cci-lc, esa-cci-lc-netcdf, fws-nwi, noaa-climate-normals-tabular, noaa-climate-normals-netcdf, goes-glm, cil-gdpcir-cc-by-sa, cil-gdpcir-cc0, cil-gdpcir-cc-by, noaa-cdr-sea-surface-temperature-whoi-netcdf, sentinel-5p-l2-netcdf, sentinel-3-olci-wfr-l2-netcdf, noaa-cdr-ocean-heat-content-netcdf, sentinel-3-synergy-aod-l2-netcdf, met-office-uk-deterministic-pressure, sentinel-3-synergy-v10-l2-netcdf, sentinel-3-olci-lfr-l2-netcdf, sentinel-3-sral-lan-l2-netcdf, sentinel-3-slstr-lst-l2-netcdf, sentinel-3-slstr-wst-l2-netcdf, sentinel-3-sral-wat-l2-netcdf, sentinel-3-slstr-frp-l2-netcdf, sentinel-3-synergy-syn-l2-netcdf, sentinel-3-synergy-vgp-l2-netcdf, sentinel-3-synergy-vg1-l2-netcdf, met-office-global-deterministic-near-surface, met-office-uk-deterministic-near-surface, met-office-uk-deterministic-height, met-office-global-deterministic-pressure, met-office-global-deterministic-height, met-office-uk-deterministic-whole-atmosphere, met-office-global-deterministic-whole-atmosphere

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

Checklist:

Please delete options that are not relevant.

• I have performed a self-review
• Changelog has been updated
• Documentation has been updated
• Unit tests pass locally (./scripts/test)
• Code is linted and styled (./scripts/format)

[ghidalgo3]

Some of the collections are failing STAC validation when ingested in to a GeoCatalog but we can fix those later. Thanks for this Pete!