a gallery is a carousel

It always rendered as one — data-carousel, a snap track, two arrows, driven by
carousel.client.js. The entity was the last thing still calling it something
else, and that collided with the site's own Gallery section: two nav rows
reading Gallery and Galleries, meaning a list of objects and a list of
photograph sets.

GalleriesPanel, GalleryPicker and GalleryItems become Carousels*, the endpoint
becomes /fofos-admin/carousels, the block kind becomes carousel and
subject-gallery becomes subject-carousel. The publish allowlist follows the
renamed tables.

What did NOT move: GALLERY_CONFIG at /fofos-admin/gallery, subjects.ts's
base '/gallery', and home_gallery_media. Those are the Gallery section and the
legacy rows, and both are correct.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

web/sections/RecordsPanel.tsx

@@ -42,7 +42,7 @@ type RecordRow = { id: number; title: string; sort_order: number } & Record<stri
  * A thumbnail URL, authenticated by `?token=`.
  *
  * An `<img>` cannot send an Authorization header, which is why `user-middleware` and the permission
- * gate both accept the token in the query string. The same thing GalleriesPanel and the file browser
+ * gate both accept the token in the query string. The same thing CarouselsPanel and the file browser
  * do — built without it first, and every picture 401s while the layout looks perfectly correct.
  */
 const thumbUrl = (path: string): string => {