Add admin-invited signups and email notifications (Gitea issue #15)

Site admins can invite a brand-new person by email from the Admin portal
Users tab -- a signup-link email lets them set their own username/password
and lands them in the app already logged in. Existing users invited to a
room now also get an email. Closes the "invited but never notified" gap
from both directions.

SMTP is configured through the Admin Settings tab at runtime (not the env
file), persisted in a new smtp_settings table with the password encrypted
at rest via a Fernet key derived from SESSION_SECRET -- the first
reversible secret this app stores in the database. A "send test email"
button surfaces real delivery errors; the invite/notification paths
themselves never fail loudly, since an SMTP outage shouldn't block an
action that already succeeded in the database.

New site_invites table mirrors RoomInvite's shape but targets an email
address with no room context; the raw signup token is hashed the same way
API tokens are, and only ever exists in the email link. POST /api/signup
is the first genuinely public, unauthenticated account-creation endpoint
in this app, reusing the existing register_user path for identical
validation.

DEPLOYMENT.md

@@ -169,6 +169,12 @@ sudo -u chatapp /srv/chatapp/backend/.venv/bin/python -m app.cli generate-vapid-
 # paste the three printed lines into /etc/chatapp/env
 ```
 
+Optional: outgoing email (admin-invited signups, room-invite notifications).
+Unlike everything else on this page, SMTP is **not** configured here —
+it's set through the Admin portal's Settings tab at runtime, no redeploy or
+env file edit needed. Skipped silently (logged, not an error) until an
+admin sets it up.
+
 ### 3d. Frontend build
 
 `backend/app/main.py` serves `frontend/dist` directly (alongside `/api` and