Merged PR 5353: Switch int_core__booking_summary to int_booking_summary

# Description

This PR does the following:
* Moves `core/int_core__booking_summary` to `cross/int_core__booking_summary`
* Renames the model `cross/int_core__booking_summary` to `cross/int_booking_summary`
* Same for schema entry. In the new schema, I just added in the description how to retrieve exclusively New Dash Bookings for usability purposes.

Then, it adapts any dependency on `int_core__booking_summary` to `int_booking_summary`

No additional changes - inclusion of Resolution Incidents data will come later in a different 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: #30676

models/intermediate/cross/int_flagging_booking_categorisation.sql

@@ -18,7 +18,7 @@
 
 {{ config(materialized="table") }}
 with
-    int_core__booking_summary as (select * from {{ ref("int_core__booking_summary") }}),
+    int_booking_summary as (select * from {{ ref("int_booking_summary") }}),
     int_resolutions__incidents as (
         select * from {{ ref("int_resolutions__incidents") }}
     ),
@@ -66,7 +66,7 @@ with
                 then false
                 else null
             end as is_booking_flagged_as_risk
-        from int_core__booking_summary
+        from int_booking_summary
         where
             -- Bookings from New Dash users with Id Deal
             is_user_in_new_dash = true