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/reporting/general/new_dash_booking_summary.sql

@@ -1,5 +1,5 @@
 with
-    int_core__booking_summary as (select * from {{ ref("int_core__booking_summary") }}),
+    int_booking_summary as (select * from {{ ref("int_booking_summary") }}),
     int_core__deal as (select * from {{ ref("int_core__deal") }}),
     int_hubspot__deal as (select * from {{ ref("int_hubspot__deal") }})
 
@@ -37,7 +37,7 @@ select
     b.has_deposit_management_service_business_type
     as has_deposit_management_service_business_type,
     b.has_protection_service_business_type as has_protection_service_business_type
-from int_core__booking_summary b
+from int_booking_summary b
 left join int_core__deal d on b.id_deal = d.id_deal
 left join int_hubspot__deal hd on b.id_deal = hd.id_deal
 -- Select only New Dash bookings