chore(billing,webapp): raise default private link connection limit to 4

Raise the default private connection limit per organization from two to four, and update the private networking docs to match.

Mono-RevId: 6d9370a136b9e4f751a62f843a992b815fd12770

Author: 0ski

apps/webapp/app/routes/_app.orgs.$organizationSlug.settings.private-connections._index/route.tsx

@@ -195,7 +195,7 @@ export default function Page() {
   });
 
   const hasPrivateNetworking = plan?.v3Subscription?.plan?.limits?.hasPrivateNetworking ?? false;
-  const limit = plan?.v3Subscription?.plan?.limits?.privateLinkConnectionLimit ?? 2;
+  const limit = plan?.v3Subscription?.plan?.limits?.privateLinkConnectionLimit ?? 4;
   const canAdd = connections.filter((c) => c.status !== "DELETING").length < limit;
   const permissionTooltip = "You don't have permission to manage private connections";
 

docs/private-networking/overview.mdx

@@ -119,7 +119,7 @@ All three conditions must be true. No organization can route traffic to another
 
 ## Limits
 
-- **Two connections per organization.** This is a soft limit — get in touch if you need more.
+- **Four connections per organization.** This is a soft limit — get in touch if you need more.
 - **All ports accepted.** Our security group allows all TCP ports from peered CIDRs. You control which ports are reachable through your NLB and target groups.
 - **Same-region or cross-region.** Connections work within the same region as your tasks or across regions (cross-region adds AWS-level cost and ~10-30ms latency).