Dev-server log cleanup: vite, Astro router, Tina schema, and npm install warnings

[jamiefolsom]

Grouped findings from a survey of fds dev boot logs (padp and marronage, both on 48a160a). None of these block anything; together they make every dev session noisy enough to hide real problems. One checklist item each — fine to split out if someone picks one up.

• Vite deprecation: optimizeDeps.esbuildOptions is set in astro.config.mjs (line 28). Vite now optimizes with Rolldown and warns on every boot; the option should move to optimizeDeps.rolldownOptions.
• Astro router warnings: getStaticPaths() ignored in dynamic page fires for [lang]/index.astro, [lang]/posts/index.astro, and [lang]/pages/[slug].astro. The pages carry getStaticPaths for the static build mode but run SSR in dev, so Astro warns once per page per session. Needs a conditional prerender export (or equivalent) keyed to build mode.
• Tina schema warning ×3: The user interface for number does not support 'list: true' — the schema generated from the site's user-defined fields maps a list-of-numbers field to a field UI Tina doesn't support.
• npm install ERESOLVE wall (~70 lines): all from @cu-mkp/editioncrafter@1.3.1, whose Material-UI 4 dependencies declare React 16/17 peers against our React 18. An overrides block in package.json would silence it honestly until EditionCrafter moves off MUI 4.

Noted but probably not worth chasing: the [@astrojs/netlify] Enabling sessions with Netlify Blobs info line (adapter default; the sites don't use Astro sessions), and the moment.defineLocale / punycode deprecations, which are transitive and will age out.

Related: the i18next debug dump (the largest noise block) is filed against react-components, since it comes from the published @performant-software/core-data bundle.