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]>

changelog.d/605-fl511-florida-cameras.md

@@ -1,8 +1,9 @@
 - Add FL511 (Florida DOT) traffic cameras as an opt-in CCTV source pack:
   the statewide ArcGIS catalog, read a page at a time under a byte cap with
   redirects refused, and frames pinned to FL511's two image hosts over HTTPS.
-  FL511's terms limit its content to individual, non-commercial use, so the
-  pack stays off unless `CCTV_FLORIDA_ENABLED=1`. Headings come from the
+  FL511's terms limit its content to individual, personal use, and any other
+  use (a public deployment included) needs FDOT's express written consent, so
+  the pack stays off unless `CCTV_FLORIDA_ENABLED=1`. Headings come from the
   catalog's direction codes, and camera ids come from the image channel, since
   the catalog's ID column repeats across regions. `CCTV_FLORIDA_MAX_SOURCES`
   sets the cap (Danielslay86, #605).