Update dbt version references to include Fusion

get-started/develop-in-lightdash/how-to-create-dimensions.mdx

@@ -88,7 +88,7 @@ For example, if I had a column in my dbt model called `source` and I wanted to a
             ...
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: Pages
@@ -152,7 +152,7 @@ You can jazz up your dimensions by configuring them in your .yml files. These di
                 ...etc
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: orders

guides/formatting-your-fields.mdx

@@ -32,7 +32,7 @@ In your dbt YAML file, it'll look something like this:
                 hidden: true
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: users
@@ -72,7 +72,7 @@ The same thing goes for metrics:
                   hidden: true
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: users
@@ -158,7 +158,7 @@ For example you might want to group the percentile metrics into two sub categori
                   groups: ['percentile', 'over']
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: events
@@ -272,7 +272,7 @@ By default, Lightdash pulls in the descriptions you've included for your dimensi
                 description: 'Unique identifier for a user'
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: users
@@ -322,7 +322,7 @@ If you don't add a custom description for your metric, Lightdash will show a des
                   description: 'Count the unique number of user IDs'
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: users
@@ -377,7 +377,7 @@ So, if I had a field `user_id_sha64`, I could relabel it to `User ID`.
                 label: 'User ID'
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: users
@@ -421,7 +421,7 @@ Same thing goes for metrics!
                   label: 'Total users'
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: users
@@ -484,7 +484,7 @@ Like this:
                 format: '0.00'
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: sales
@@ -527,7 +527,7 @@ Like this:
                   format: '0.00'
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: sales
@@ -588,7 +588,7 @@ Like this:
                 format: '0," K"'
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: sales
@@ -634,7 +634,7 @@ Like this:
                   format: '0.00,,," B"'
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: sales
@@ -698,7 +698,7 @@ You can add a `format` to your dimensions this:
                 format: '[$£]#,##0.00'
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: sales
@@ -742,7 +742,7 @@ You can add a `format` to your metrics this:
                   format: '[$£]#,##0.00'
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: sales
@@ -819,7 +819,7 @@ In your model YAML file:
                   format: '${ld.parameters.currency_symbol}0,0.00'
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: sales
@@ -898,7 +898,7 @@ In your model YAML file:
                   format: '${ld.parameters.currency=="usd"?"$":""}${ld.parameters.currency=="eur"?"€":""}${ld.parameters.currency=="eur"?"£":""}0,0.00'
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: sales
@@ -967,7 +967,7 @@ Then use it in your model YAML file:
                   format: '0,0${ld.parameters.decimals=="true"?".00":""}'
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: sales

guides/metrics-catalog.mdx

@@ -138,7 +138,7 @@ This will set the default visibility of metrics in the catalog to `show` for all
             visibility: hide
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yml
     models:
       - name: events
@@ -178,7 +178,7 @@ This will hide the events model from the catalog.
                 visibility: show
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yml
     models:
       - name: events
@@ -268,7 +268,7 @@ spotlight:
               - revenue
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yml
     models:
       - name: events
@@ -331,7 +331,7 @@ Now you can add the `marketing` category to the `event_count` metric:
                   - marketing
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yml
     models:
       - name: events
@@ -400,7 +400,7 @@ You can assign owners to metrics using the `spotlight.owner` property. The owner
                     owner: alice@yourcompany.com
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: orders
@@ -458,7 +458,7 @@ You can set a default owner for all metrics in a model. Metric-level owners over
                   # inherits bob@yourcompany.com from model
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: orders
@@ -534,7 +534,7 @@ Use boolean values at the dimension level to hide a dimension from filter or seg
                   segment_by: false  # hide from segment-by dropdown
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: orders
@@ -587,7 +587,7 @@ Use an array of dimension names at the metric level to create an allowlist of di
                       - customer_segment
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: orders
@@ -678,7 +678,7 @@ To pre-select a time field in the explore view, simply define the default settin
                   type: count
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yml
     models:
       - name: events
@@ -742,7 +742,7 @@ To pre-select a time field in the explore view, simply define the default settin
           # ... your column definitions here
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: events
@@ -806,7 +806,7 @@ This will override the time dimension defined on the table level.
                     interval: MONTH
     ```
   </Tab>
-  <Tab title="dbt v1.10+">
+  <Tab title="dbt v1.10+ and Fusion">
     ```yaml
     models:
       - name: events