Vendor Tailwind and daisyUI in the repo; never reach github.com

Builds used to download the Tailwind binary and the daisyUI plugins from GitHub
releases. They are now committed in tools/tailwind/:
- the Tailwind 4.3.3 standalone binary for linux-x64, xz -9e compressed (28 MB);
- daisyui.mjs and daisyui-theme.mjs 5.7.47;
- daisyUI's llms.txt component reference;
- Tailwind's MIT license.

tools/tailwind.sh no longer touches the network. "prepare" checks every file
against its pinned sha256 and unpacks the binary into .tools/. MSBuild reruns it
only when the archive or the script changes. A build from scratch was checked
inside a network namespace with no network at all.

.gitattributes keeps the vendored files byte-exact, and Tailwind no longer scans
tools/, whose llms.txt names every daisyUI class.

Both workflows used actions/checkout, which a Gitea runner downloads from
github.com. They now git fetch the commit from this Gitea, as they already did
for SocialPub.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LsXgEaXee4GCU1hwYgPJXw

Styles/theme.css

@@ -14,7 +14,7 @@
    --neo-strong the deeper tone used for scrollbars and selections, and --neo-lift / --neo-sink how far a
    gradient built from an arbitrary colour (a coloured .btn) moves towards white and black. */
 
-@plugin "../.tools/tailwind/daisyui-theme.mjs" {
+@plugin "../tools/tailwind/daisyui-theme.mjs" {
 	name: "neo-light";
 	default: true;
 	prefersdark: false;
@@ -64,7 +64,7 @@
 	--noise: 0;
 }
 
-@plugin "../.tools/tailwind/daisyui-theme.mjs" {
+@plugin "../tools/tailwind/daisyui-theme.mjs" {
 	name: "neo-dark";
 	default: false;
 	prefersdark: true;