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>

api/publish.ts

@@ -41,7 +41,7 @@ const CONTENT_TABLES = [
   /*
     The page builder's own tables, and the reason they are FIRST.
 
-    Parents before children: a section belongs to a page and a component to a section. `galleries` sits
+    Parents before children: a section belongs to a page and a component to a section. `carousels` sits
     below them because a gallery block names a set by id — carried in JSON rather than as a foreign
     key, so nothing enforces the order, which is exactly why it is written down.
 
@@ -60,8 +60,8 @@ const CONTENT_TABLES = [
   'home_content',
   'home_gallery_media',
   'about_content',
-  'galleries',
-  'gallery_items',
+  'carousels',
+  'carousel_items',
   'collections',
   'collection_items',
   'collection_item_media',