Add Amsterdam traffic and ANPR camera positions to the Data Library

The City of Amsterdam's verkeersinformatiesystemen register lists where
its ~500 traffic and ANPR cameras stand, with type and asset number, but
publishes no pictures. That fits a Data Library dataset better than a
CCTV pack: the register answers GeoJSON in WGS84 with CORS headers, so
the entry fetches it browser-direct with no proxy code.

The register names no licence ("public unless stated otherwise"), so the
entry stays operator opt-in, as #251 had it. The dataset and the
position-only camera idea come from @Maher-Reven's #251, which this
replaces; the entry lists them as maintainer and in its attribution.

Co-authored-by: Maher Kurdi <[email protected]>

changelog.d/1604-data-library.md

@@ -8,7 +8,9 @@
   generic `/api/library` proxy serves entries without CORS. Seeded with NASA
   EONET events, EIA and WRI power plants, NWS alerts, NOAA tide stations,
   Smithsonian volcanoes, NASA Black Marble, OpenSeaMap seamarks, and the
-  opt-in IMF PortWatch and CCTV packs. FEMA USA Structures and the
+  opt-in IMF PortWatch and CCTV packs, plus the City of Amsterdam's
+  traffic and ANPR camera positions (opt-in; contributed by @Maher-Reven in
+  #251). FEMA USA Structures and the
   National Bridge Inventory load what is in view once you zoom in, and
   Addresscloud's EPC ratings stream from Source Cooperative's GeoParquet on
   S3, coloured A–G with live legend counts. Open tile overlays (geology,