docs: Add region to requirements for peering (#9689)

Author: morgan-at-cube

docs/pages/product/deployment/cloud/vpc/aws/private-link.mdx

@@ -31,6 +31,10 @@ To request establishing a PrivateLink connection, please share the following inf
 - **Reference Name** for the record (such as "Snowflake-prod" or "clickhouse-dev")
 - **Ports**: a list of ports that will be accessed through this connection
 - **DNS Name** (optional): an internal DNS name of the upstream service in case SSL needs to be supported
+- **Dedicated Infrastructure Region:** VPC Peering requires Cube to be hosted in 
+    [dedicated infrastructure][dedicated-infra]. Please specify what region the Cube Cloud 
+    dedicated infrastructure should be hosted in.
+
 
 If a DNS name is provided, an internal DNS record will be created pointing at the established PrivateLink
 connection, and the service will be addressable by that name inside the Cube Cloud infrastructure.
@@ -48,3 +52,4 @@ supplied DNS Name or an AWS internal DNS name returned to you by the Cube team.
 
 [aws-docs-private-link]: https://aws.amazon.com/privatelink/
 [aws-docs-endpoint-service]: https://docs.aws.amazon.com/vpc/latest/privatelink/configure-endpoint-service.html
+[dedicated-infra]: /product/deployment/cloud/infrastructure#dedicated-infrastructure

docs/pages/product/deployment/cloud/vpc/aws/vpc-peering.mdx

@@ -18,6 +18,9 @@ information is required:
   example, `vpc-0099aazz`
 - **AWS VPC CIDR:** The [CIDR block][wiki-cidr-block] of the VPC that Cube Cloud
   will connect to, for example, `10.0.0.0/16`
+- **Dedicated Infrastructure Region:** VPC Peering requires Cube to be hosted in 
+  [dedicated infrastructure][dedicated-infra]. Please specify what region the Cube Cloud 
+  dedicated infrastructure should be hosted in.
 
 ## Setup
 
@@ -129,6 +132,7 @@ Customer Success Manager and share with them the following:
 [aws-docs-vpc-peering]:
   https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html
 [aws-docs-vpc-security-group]: https://docs.aws.amazon.com/vpc/latest/userguide/security-group-rules.html
+[dedicated-infra]: /product/deployment/cloud/infrastructure#dedicated-infrastructure
 [wiki-cidr-block]:
   https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_blocks
 

docs/pages/product/deployment/cloud/vpc/azure.mdx

@@ -1,15 +1,5 @@
 # Connecting with a VPC on Azure
 
-## Prerequisites
-
-To allow Cube Cloud to connect to a Virtual Network on Azure, the following
-information is required:
-
-- **Virtual Network Name:** This can be found in the Virtual Networks section of
-  the [Azure Portal][azure-console].
-- **Tenant ID:** This can be found under&nbsp;<Btn>Azure Active Directory</Btn>
-  →&nbsp;<Btn>Properties</Btn> →&nbsp;<Btn>Tenant ID</Btn> in the [Azure Portal][azure-console].
-
 ## Setup
 
 For cross-tenant peering in Azure, you are supposed to assign the peering role
@@ -91,6 +81,9 @@ information:
 - **Tenant ID:** You can find it in&nbsp;<Btn>Azure Active Directory</Btn>
   →&nbsp;<Btn>Properties</Btn> →&nbsp;<Btn>Tenant ID</Btn> section of
   [Azure Portal][azure-console].
+- **Dedicated Infrastructure Region:** VPC Peering requires Cube to be hosted 
+  in [dedicated infrastructure][dedicated-infra]. Please specify what region 
+  the Cube Cloud dedicated infrastructure should be hosted in.
 
 ## Supported Regions
 
@@ -99,3 +92,4 @@ We support all general-purpose regions. Cube Store is currently located only in
 proximity to it.
 
 [azure-console]: https://portal.azure.com
+[dedicated-infra]: /product/deployment/cloud/infrastructure#dedicated-infrastructure

docs/pages/product/deployment/cloud/vpc/gcp.mdx

@@ -2,9 +2,12 @@
 
 Work with your Cube sales or customer success team to initiate this process.
 
-- [Sign up for a Cube Cloud account][cube-cloud-signup] if you haven't already.
-- Let the Cube team know your Cube Cloud tenant name (e.g. example.cubecloud.dev) and your desired GCP region for the deployment.  For best performance, select one of the "Supported Regions" listed below.
-- Cube will provision the VPC and provide the following information you can use to create the peering request:
+- VPC Peering requires Cube to be hosted in [dedicated infrastructure][dedicated-infra]. 
+Let the Cube team know your Cube Cloud tenant name (e.g. example.cubecloud.dev) and what region 
+the dedicated infrastructure should be hosted in. 
+For best performance, select one of the "Supported Regions" listed below.
+- Cube will provision the dedicated VPC and provide the following 
+information you can use to create the peering request:
   - [Google Cloud Project ID][gcp-docs-projects]
   - Google Cloud VPC Network Name
 
@@ -48,3 +51,4 @@ run the [Cloud SQL Auth Proxy][gcp-cloudsql-auth-proxy].
   https://cloud.google.com/resource-manager/docs/creating-managing-projects#before_you_begin
 [gcp-docs-vpc-peering]: https://cloud.google.com/vpc/docs/vpc-peering
 [cube-cloud-signup]: https://cubecloud.dev/auth/signup
+[dedicated-infra]: /product/deployment/cloud/infrastructure#dedicated-infrastructure