add link to default services matrix on each resource page

Author: davemooreuws

docs/apis.mdx

@@ -1308,3 +1308,7 @@ accountsApi.get("/orgs/:id", (ctx) async {
 ```
 
 </CodeSwitcher>
+
+## Default Cloud Services
+
+Each cloud provider comes with a set of default services used when deploying resources. You can find the full list of these default cloud services in the [Deploy documentation: Default Cloud Services](/providers#default-cloud-services).

docs/batch.mdx

@@ -239,3 +239,7 @@ void main() {
 ```
 
 </CodeSwitcher>
+
+## Default Cloud Services
+
+Each cloud provider comes with a set of default services used when deploying resources. You can find the full list of these default cloud services in the [Deploy documentation: Default Cloud Services](/providers#default-cloud-services).

docs/http.mdx

@@ -53,3 +53,7 @@ http(bootstrap)
 </TabItem>
 
 </Tabs>
+
+## Default Cloud Services
+
+Each cloud provider comes with a set of default services used when deploying resources. You can find the full list of these default cloud services in the [Deploy documentation: Default Cloud Services](/providers#default-cloud-services).

docs/keyvalue.mdx

@@ -437,3 +437,7 @@ keys.forEach((String key) {
 ```
 
 </CodeSwitcher>
+
+## Default Cloud Services
+
+Each cloud provider comes with a set of default services used when deploying resources. You can find the full list of these default cloud services in the [Deploy documentation: Default Cloud Services](/providers#default-cloud-services).

docs/messaging.mdx

@@ -702,3 +702,7 @@ await Future.wait(messages.map((message) async {
 It's common to ask when to use a queue or a topic. From a publisher's point of view, both queues and topics are almost identical. The difference is primarily on the receiver/subscriber side. Topics push new messages to their subscribers, immediately spinning up workers to process them, while queues rely on the receiver to ask for new messages to process.
 
 For these reasons, we usually default to Topics. Queues are more suitable for batch workloads or situations where there are occasional surges of requests that can be processed at a later time.
+
+## Default Cloud Services
+
+Each cloud provider comes with a set of default services used when deploying resources. You can find the full list of these default cloud services in the [Deploy documentation: Default Cloud Services](/providers#default-cloud-services).

docs/schedules.mdx

@@ -398,3 +398,7 @@ If you're using schedules on Azure you will be charged for at least 1 container
   This may change in the future as Nitric's Azure provider evolves, allowing for
   scale to zero as is the case with other providers.
 </Note>
+
+## Default Cloud Services
+
+Each cloud provider comes with a set of default services used when deploying resources. You can find the full list of these default cloud services in the [Deploy documentation: Default Cloud Services](/providers#default-cloud-services).

docs/secrets.mdx

@@ -312,3 +312,7 @@ final value = latest.value;
 ```
 
 </CodeSwitcher>
+
+## Default Cloud Services
+
+Each cloud provider comes with a set of default services used when deploying resources. You can find the full list of these default cloud services in the [Deploy documentation: Default Cloud Services](/providers#default-cloud-services).

docs/sql.mdx

@@ -336,3 +336,7 @@ Here are a few alternatives that work well with Nitric:
 - [PlanetScale](https://planetscale.com/) (MySQL)
 
 Guides are available for some of these alternatives in the [guides section](/guides).
+
+## Default Cloud Services
+
+Each cloud provider comes with a set of default services used when deploying resources. You can find the full list of these default cloud services in the [Deploy documentation: Default Cloud Services](/providers#default-cloud-services).

docs/storage.mdx

@@ -675,3 +675,7 @@ profiles.on(BlobEventType.delete, "*", (ctx) async {
 ```
 
 </CodeSwitcher>
+
+## Default Cloud Services
+
+Each cloud provider comes with a set of default services used when deploying resources. You can find the full list of these default cloud services in the [Deploy documentation: Default Cloud Services](/providers#default-cloud-services).

docs/websockets.mdx

@@ -459,3 +459,7 @@ socket.onMessage((ctx) async {
   Do not send messages to a connection during it's `connect` callback, if you
   need to acknowledge connection, do so by using a [topic](./messaging)
 </Note>
+
+## Default Cloud Services
+
+Each cloud provider comes with a set of default services used when deploying resources. You can find the full list of these default cloud services in the [Deploy documentation: Default Cloud Services](/providers#default-cloud-services).