Inline the error layout's own rules beside the app's build

Plan step 46, from SealShare's breakpoint walk: an application imports
the stylesheets its own views render, and none renders the error layout,
so under a real build its 403/404/500 pages drew unstyled. With a build
the page now keeps the app's Vite tags (foundation, tokens, scheme, font)
and inlines Stylesheets::bundle() of components/error-page.css and its
imports beside them (ErrorPage::layoutStyles(), cached). Without a build
the fallback is unchanged. An application imports nothing for its error
pages; one that imports all.css gets the same layered rules twice, which
is harmless.

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

config/livewire-material.php

@@ -197,8 +197,10 @@ return [
     | pages pass @vite() only the entries that are not a stylesheet: their
     | CSS is a bundle of their own (all.css, showcase.css and the scheme,
     | served by ShowcaseAssetController), so they need nothing from the
-    | application's build. The error pages have no such bundle, so
-    | ErrorPage::assets() passes this whole list, CSS included, to @vite().
+    | application's build. The error pages pass this whole list, CSS
+    | included, to @vite() (ErrorPage::assets()) for the foundation, scheme
+    | and font, and inline their own layout's rules beside it
+    | (ErrorPage::layoutStyles()), so the entry needs no import for them.
     |
     */