add Supporter Providers to more concept pages

Author: jordanstephens

docs/concepts/configuration.md

@@ -89,3 +89,12 @@ Here are the different ways sensitive config values are stored depending on the
 :::info
 Please note that while Defang supports setting sensitive config, it does not support the [`secrets`](https://docs.docker.com/reference/compose-file/secrets/) top-level element as seen in the Compose specification. Please see our [Compose](/docs/concepts/compose) page for more details.
 :::
+
+## Supported Providers
+
+| Provider       | Config Support |
+|----------------|:--------------:|
+| Playground     |     ✅ |
+| AWS            |     ✅ |
+| DigitalOcean   |     ✅ |
+| GCP            |     ✅ |

docs/concepts/estimation.md

@@ -64,3 +64,12 @@ Now that you have estimated the costs associated with your project. You are read
 defang compose up [--provider aws|gcp|digitalocean] [--mode affordable|balanced|high_availability]
 ```
 
+## Supported Providers
+
+| Provider       | Estimation Support |
+|----------------|:------------------:|
+| Playground     |     ❌ |
+| AWS            |     ✅ |
+| DigitalOcean   |     ❌ |
+| GCP            |     ✅ |
+

docs/concepts/railpack.md

@@ -144,3 +144,12 @@ services:
         reservations:
           memory: 512M
 ```
+
+## Supported Providers
+
+| Provider       | Railpack Support |
+|----------------|:----------------:|
+| Playground     |     ❌ |
+| AWS            |     ✅ |
+| DigitalOcean   |     ❌ |
+| GCP            |     ✅ |

docs/concepts/resources.md

@@ -67,7 +67,7 @@ Defang uses `shm_size` to configure both the memory and disk space available to
 
 The default `shm_size` values for each platform are as follows. More or less may be specified.
 
-| Platform      | `shm_size` Minimum |
+| Provider      | `shm_size` Minimum |
 | ------------- | ------------------ |
 | AWS           | 16G                |
 | Digital Ocean | 8G                 |

docs/concepts/scaling.md

@@ -65,10 +65,10 @@ Auto-scaling systems typically rely on:
   - If average CPU > 85% for 5 minutes → scale up by 2 instances.
 - **Cooldown Periods**: Delays between scaling events to prevent rapid, repeated changes (flapping).
 
-### Supported Platforms
+### Supported Providers
 
-| Platform        | Auto-Scaling Support |
-|----------------|:----------------------:|
+| Provider       | Auto-Scaling Support |
+|----------------|:--------------------:|
 | Playground     |     ❌ |
 | AWS            |     ✅ |
 | DigitalOcean   |     ❌ |