docs(wiki): bring the pages in line with 4.3.0

Every page was read against the code on dev. What changed:

- Pages that described 4.2 behaviour: satellite view on the vector maps,
  the mobile journal timeline, Collab with its fifth tab, the Review badge,
  clustered pins on the share page, the Leaflet preset list, the strict
  guard on fe80::/10, the invite link tools and their scopes, the Public
  API scope rules, the permission count in the plugin SDK.
- Features of this release that no page mentioned: videos in a journal
  entry, receipts on an expense, the Google transit backend, routing
  counters, the rating on a place, the navigation menu, car stops, the
  manual school holiday catalogue and its MCP tools, the Dawarich panel in
  the Atlas, the release notes modal, plugin frames going fullscreen, the
  corridor call into the search provider hook.
- Statements that sent an admin the wrong way: DEFAULT_LANGUAGE is not in
  the Helm ConfigMap, env.PORT cannot be changed on the chart alone, the
  rotation script does not cover the document sync credentials, event
  handlers cannot broadcast, there is no per user MFA reset in the admin
  panel, the demo user can edit, an unparsable APP_URL stops the server.
- Updating gets a section for 4.3.0: the TREK Places API as the new
  default, the new variables, the Overpass timeout, SSO sessions on an
  OIDC only instance, the migration that puts booked nights on the drive.

wiki/Plugin-Cookbook.md

@@ -137,6 +137,16 @@ whatever happens, so a provider that misses that window is left out of the list
 than holding it up. `near` is the coordinate the search is biased toward,
 and it is what tells the four places called "Hase-dera" apart — use it when you have it.
 
+The Road trip search along the route reaches the same hook. It calls `search` once per
+kind the person picked, with two more fields on the request: `category` (`fuel`,
+`charging`, `rest_area`, `campsite`, `restaurant`, `sights` or `hotel`) and `bounds`
+(`{ south, west, north, east }`, the rectangle to search, with `near` at its centre).
+`query` is then a fixed English phrase such as `EV charging station` rather than
+something typed, so an index that ignores `category` still gets a usable query. Hits
+outside `bounds` are dropped, and so is a hit whose own `category` names a different one
+of those seven kinds. Both fields are absent on ordinary searches, so read them as
+optional.
+
 ## Raise validation warnings on a trip
 
 **Needs:** `hook:trip-warning-provider`