Merged PR 4335: Rework new dash attribution using booking summary

# Description

Changes:
* On Created and Check Out Bookings daily models, the determination of New Dash bookings now uses `int_core__booking_summary`. This does not change the output, but will be more consistent for other KPIs.
* Adds the categorisation of `dash_source` in all daily metric models that depend on Verification Requests (Guest Journeys). This affects GJ Created, GJ Started, GJ Completed, GJ w. Payment and Guest Payments. Note that the next aggregations (monthly, mtd, agg_monthly, agg_mtd) are not created yet. This will be done in a separated PR.

# Checklist

- [X] The edited models and dependants run properly with production data.
- [X] The edited models are sufficiently documented.
- [X] The edited models contain PK tests, and I've ran and passed them.
- [X] I have checked for DRY opportunities with other models and docs.
- [X] I've picked the right materialization for the affected models.

# Other

- [ ] Check if a full-refresh is required after this PR is merged.

Related work items: #27356

models/intermediate/kpis/schema.yml

@@ -967,13 +967,15 @@ models:
       The unique key corresponds to the deepest granularity of the model,
       in this case: 
       - date, 
-      - id_deal.
+      - id_deal,
+      - dash_source
 
     data_tests:
       - dbt_utils.unique_combination_of_columns:
           combination_of_columns:
             - date
             - id_deal
+            - dash_source
 
     columns:
       - name: date
@@ -988,6 +990,16 @@ models:
         data_tests:
           - not_null
 
+      - name: dash_source
+        data_type: string
+        description: Dashboard source, either old or new.
+        data_tests:
+          - not_null
+          - accepted_values:
+              values:
+                - "New Dash"
+                - "Old Dash"
+
       - name: active_accommodations_per_deal_segmentation
         data_type: string
         description: |
@@ -1271,13 +1283,15 @@ models:
       The unique key corresponds to the deepest granularity of the model,
       in this case: 
       - date, 
-      - id_deal.
+      - id_deal,
+      - dash_source
 
     data_tests:
       - dbt_utils.unique_combination_of_columns:
           combination_of_columns:
             - date
             - id_deal
+            - dash_source
 
     columns:
       - name: date
@@ -1292,6 +1306,16 @@ models:
         data_tests:
           - not_null
 
+      - name: dash_source
+        data_type: string
+        description: Dashboard source, either old or new.
+        data_tests:
+          - not_null
+          - accepted_values:
+              values:
+                - "New Dash"
+                - "Old Dash"
+
       - name: active_accommodations_per_deal_segmentation
         data_type: string
         description: |
@@ -1575,13 +1599,15 @@ models:
       The unique key corresponds to the deepest granularity of the model,
       in this case: 
       - date, 
-      - id_deal.
+      - id_deal,
+      - dash_source.
 
     data_tests:
       - dbt_utils.unique_combination_of_columns:
           combination_of_columns:
             - date
             - id_deal
+            - dash_source
 
     columns:
       - name: date
@@ -1596,6 +1622,16 @@ models:
         data_tests:
           - not_null
 
+      - name: dash_source
+        data_type: string
+        description: Dashboard source, either old or new.
+        data_tests:
+          - not_null
+          - accepted_values:
+              values:
+                - "New Dash"
+                - "Old Dash"
+
       - name: active_accommodations_per_deal_segmentation
         data_type: string
         description: |
@@ -1879,13 +1915,15 @@ models:
       The unique key corresponds to the deepest granularity of the model,
       in this case: 
       - date, 
-      - id_deal.
+      - id_deal,
+      - dash_source
 
     data_tests:
       - dbt_utils.unique_combination_of_columns:
           combination_of_columns:
             - date
             - id_deal
+            - dash_source
 
     columns:
       - name: date
@@ -1900,6 +1938,16 @@ models:
         data_tests:
           - not_null
 
+      - name: dash_source
+        data_type: string
+        description: Dashboard source, either old or new.
+        data_tests:
+          - not_null
+          - accepted_values:
+              values:
+                - "New Dash"
+                - "Old Dash"
+
       - name: active_accommodations_per_deal_segmentation
         data_type: string
         description: |
@@ -2184,7 +2232,8 @@ models:
       in this case: 
       - date, 
       - id_deal,
-      - has_id_check.
+      - has_id_check,
+      - dash_source
 
     data_tests:
       - dbt_utils.unique_combination_of_columns:
@@ -2192,6 +2241,7 @@ models:
             - date
             - id_deal
             - has_id_check
+            - dash_source
 
     columns:
       - name: date
@@ -2206,6 +2256,16 @@ models:
         data_tests:
           - not_null
 
+      - name: dash_source
+        data_type: string
+        description: Dashboard source, either old or new.
+        data_tests:
+          - not_null
+          - accepted_values:
+              values:
+                - "New Dash"
+                - "Old Dash"
+
       - name: has_id_check
         data_type: string
         description: Does the verification in the guest journey