feat: add Team billing tier

Widens the tier enum from free/pro to free/pro/team and every
"free" | "pro" cast that assumed exactly two tiers (~30 call sites:
every AI route's withAiQuota/checkAndIncrementTierLimit call, admin
user/invite management, upload quota checks, OpenAPI schemas). Team
sits above Pro with genuinely unlimited recipes/public-recipes (the
-1 sentinel, which Pro doesn't actually use — Pro uses large finite
numbers instead) and a higher AI-call/storage cap. Seeded via
db:seed, editable afterward from Admin > Tiers.

role (user/moderator/admin — permissions) and tier (free/pro/team —
billing limits) stay separate concepts, as they already were; this
does not touch role-based permissions.

Requires migration 0043 to run against a live DB — not applied in
this sandbox (no Docker here); run `pnpm db:migrate` then `pnpm db:seed`.

v0.44.0

apps/web/components/admin/invites-manager.tsx

@@ -24,7 +24,7 @@ type Invite = {
   token: string;
   email: string | null;
   role: "user" | "moderator" | "admin";
-  tier: "free" | "pro";
+  tier: "free" | "pro" | "team";
   createdAt: string;
   expiresAt: string | null;
 };
@@ -33,7 +33,7 @@ export function InvitesManager({ invites, appUrl }: { invites: Invite[]; appUrl:
   const router = useRouter();
   const [email, setEmail] = useState("");
   const [role, setRole] = useState<"user" | "moderator" | "admin">("user");
-  const [tier, setTier] = useState<"free" | "pro">("free");
+  const [tier, setTier] = useState<"free" | "pro" | "team">("free");
   const [creating, setCreating] = useState(false);
   const [revokeId, setRevokeId] = useState<string | null>(null);
 
@@ -106,6 +106,7 @@ export function InvitesManager({ invites, appUrl }: { invites: Invite[]; appUrl:
               <SelectContent>
                 <SelectItem value="free">Free</SelectItem>
                 <SelectItem value="pro">Pro</SelectItem>
+                <SelectItem value="team">Team</SelectItem>
               </SelectContent>
             </Select>
           </div>