Merged PR 5191: Guest Journey Payments to reporting

# Description

Guest Journey Payments to reporting. This aims to substitute core__verification_payments_v2, which is in use in the report of Guest Payments within Business Overview.

In order to avoid re-doing PBI work, I already set  id_guest_product_payment as text for future usage. Similarly, superhog fees are called truvi fees.

# 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: #30024

models/intermediate/core/schema.yml

@@ -6063,9 +6063,19 @@ models:
 
     columns:
       - name: id_guest_product_payment
-        data_type: bigint
+        data_type: text
         description: |
           Unique identifier for the guest product payment.
+          It's a built-in ID that concatenates the original ID with a prefix 
+          depending on the source, to avoid clashes. This ID does not make 
+          sense outside of DWH.
+          The prefix used is "leg_" for "legacy" Verification To Payment,
+          which corresponds to the historical CheckInCover that were considered 
+          as verification payment, rather than Guest Products.
+          For the Guest Product Payments that follow the usual Guest Product 
+          flow, no prefix is added. However, keep in mind that the field is 
+          in text format.
+
         data_tests:
           - unique
           - not_null
@@ -6580,7 +6590,7 @@ models:
           It's a built-in unique ID that means nothing outside DWH. 
           It combines the id_verification_product_payment and the 
           id_guest_journey_payment into a unique ID by adding the prefix 
-          gpp for Guest Product Payments and vpp for Verification Product 
+          "gpp" for Guest Product Payments and "vpp" for Verification Product 
           Payments.
         data_tests:
           - unique
@@ -6629,9 +6639,18 @@ models:
               where: "guest_journey_product_type = 'GUEST_PRODUCT'"
 
       - name: id_guest_product_payment
-        data_type: bigint
+        data_type: text
         description: |
           The ID for Guest Product Payments. 
+          It's a built-in ID that concatenates the original ID with a prefix 
+          depending on the source, to avoid clashes. This ID does not make 
+          sense outside of DWH.
+          The prefix used is "leg_" for "legacy" Verification To Payment,
+          which corresponds to the historical CheckInCover that were considered 
+          as verification payment, rather than Guest Products.
+          For the Guest Product Payments that follow the usual Guest Product 
+          flow, no prefix is added. However, keep in mind that the field is 
+          in text format.
           It cannot be null for Product Types equal to GUEST_PRODUCT. 
           It's null for Product Types equal to VERIFICATION_PRODUCT.
         data_tests: