fix(cctv): FL511 written-consent wording and robust catalog paging

- State FL511's terms the same way everywhere: individual, personal use
  only, and any other use (a public deployment included) needs FDOT's
  express written consent. .env.example, README, dataCredits, the source
  licence string, the catalog comment and the changelog fragment said only
  "individual, non-commercial use".
- Page the ArcGIS catalog on exceededTransferLimit alone and advance the
  offset by the rows each page returned, so a lower server-side max
  record count no longer cuts the catalog short at the first short page.
- Order pages by OBJECTID_1 (this layer's object id; a plain OBJECTID is
  rejected with HTTP 400) so offset paging is stable.
- Raise the page ceiling to 40 and warn when it is hit.
- Tests: short pages with exceededTransferLimit keep paging, orderByFields
  is sent, and a service that ignores resultOffset stops at the ceiling.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

server/providers/cctv/constants.js

@@ -122,6 +122,8 @@ export const FLORIDA_IMAGE_HOSTS = [
 export const DEFAULT_FLORIDA_MAX_SOURCES = 500;
 /** Byte cap per catalog page (2,000 rows, about 650 KiB measured). */
 export const FLORIDA_MAX_CATALOG_BYTES = 2 * 1024 * 1024;
+/** Catalog page ceiling: 40 pages covers 4,000+ cameras even at 100 rows a page. */
+export const FLORIDA_MAX_CATALOG_PAGES = 40;
 export const FLORIDA_ANCHORS = [
   { lat: 25.7617, lon: -80.1918 }, // Miami
   { lat: 28.5384, lon: -81.3789 }, // Orlando