Add Feedback domain module: public submission flow, admin CRUD, reporting

New /feedback API domain backed by its own FEEDBACK_DB, mirroring the
Calendar domain's router -> service -> DB pool layering:

- Public endpoints (no auth): eligible-events listing, event config,
  submission with honeypot + rate limiting (in-memory + DB backstop).
- Admin endpoints (session-header auth, reusing Calendar's users/sessions
  via a swappable feedback.auth.ts boundary): events/songs/questions CRUD,
  bulk reorder/assignment, aggregated reporting, CSV export.
- Schema in sql/feedback/001_init.sql (8 tables), applied and verified
  against the real FEEDBACK_DB.
- 64 Jest tests covering validation, auth, rate limiting, CSV escaping,
  and report aggregation (pure functions, no DB needed).

Includes fixes from a security review: path traversal defense doesn't
apply here (that's the frontend proxy, separate repo), but the
rate-limiter cluster does - recordSubmission now counts every processed
request (not just successful ones), the in-memory Map evicts empty
entries instead of growing unbounded, FEEDBACK_IP_SALT is required at
boot instead of silently degrading to unsalted hashing, and submission
answer/rating arrays are capped and de-duplicated to bound insert
amplification.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

test/feedback/honeypot.test.ts

@@ -0,0 +1,16 @@
+import {isHoneypotTriggered} from '../../src/models/feedback/public/public.router';
+
+describe('isHoneypotTriggered', () => {
+	it('is false when the field is absent', () => {
+		expect(isHoneypotTriggered({})).toBe(false);
+	});
+
+	it('is false when the field is empty', () => {
+		expect(isHoneypotTriggered({website: ''})).toBe(false);
+		expect(isHoneypotTriggered({website: '   '})).toBe(false);
+	});
+
+	it('is true when a bot filled it in', () => {
+		expect(isHoneypotTriggered({website: 'https://spam.example'})).toBe(true);
+	});
+});