Merged PR 3221: Adapted lifecycle logic for deals to include offboardings

# Description

Adapts deals lifecycle logic by including offboardings from hubspot. It mostly increases the number of churning and inactive states in decrement of active state.
I also updated documentation and added an accepted values test.

When deploying and refreshing prod, figures in main kpis will be impacted

# 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.
- [NA] I have checked for DRY opportunities with other models and docs.
- [NA] 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: #22689

models/intermediate/cross/schema.yml

@@ -1404,13 +1404,13 @@ models:
       deal regarding its activity. This information is encapsulated in the following columns:
 
       deal_lifecycle_state: contains one of the following states
-      - 01-New: Deals that have been created in the current month, without bookings
-      - 02-Never Booked: Deals that have been created before the current month, without bookings. 
-      - 03-First Time Booked: Deals that have been booked for the first time in the current month.
-      - 04-Active: Deals that have booking activity in the past 12 months (that are not FTB nor reactivated) 
-      - 05-Churning: Deals that are becoming inactive because of lack of bookings in the past 12 months
-      - 06-Inactive: Deals that have not had a booking for more than 12 months. 
-      - 07-Reactivated: Deals that have had a booking in the current month that were inactive or churning before.
+      - 01-New: Deals that have been created in the current month, without bookings, that are not offboarded.
+      - 02-Never Booked: Deals that have been created before the current month, without bookings, that are not offboarded.
+      - 03-First Time Booked: Deals that have been booked for the first time in the current month, that are not offboarded.
+      - 04-Active: Deals that have booking activity in the past 12 months (that are not FTB nor reactivated), that are not offboarded.
+      - 05-Churning: Either Deals that are offboarded in that month or Deals that are becoming inactive because of lack of bookings in the past 12 months
+      - 06-Inactive: Either Deals that have been previously offboarded or Deals that have not had a booking for more than 12 months. 
+      - 07-Reactivated: Deals that have had a booking in the current month that were inactive or churning before, that are not offboarded.
       - Finally, if none of the logic applies, which should not happen, null will be set and a dbt alert will raise.
 
       Since the states of Active, First Time Booked and Reactivated indicate certain booking activity and are
@@ -1422,6 +1422,12 @@ models:
       Note that if a deal has had a booking created in a given month, all 3 columns will be true. Similarly,
       if the last booking created to a deal was 5 months ago, only the column has_been_booked_in_1_month 
       will be false; while the other 2 will be true.
+      Some final considerations:
+      - It's possible but not common that a Deal gets offboarded on the same month that has had some bookings created. 
+      - It shouldn't happen that a Deal that is Inactive has some bookings created. However, there's few cases in which 
+        this happens likely because of misconfiguration between Hubspot and Core. This should be reported to increase 
+        data quality.
+
     tests:
       - dbt_utils.unique_combination_of_columns:
           combination_of_columns:
@@ -1466,6 +1472,12 @@ models:
           on the lifecycle. Can be null if the deal has never had a booking associated with it or if
           the deal only had 1 booking in its history.
 
+      - name: cancellation_date_utc
+        data_type: date
+        description: |
+          Date of when the deal was cancelled, according to Hubspot. This is the date we're considering 
+          for hard offboarding. It can be null, meaning the account has not been offboarded.
+
       - name: deal_lifecycle_state
         data_type: character varying
         description: |
@@ -1474,6 +1486,15 @@ models:
           07-Reactivated. Failing to implement the logic will result in alert.
         tests:
           - not_null
+          - accepted_values:
+              values:
+                - 01-New
+                - 02-Never Booked
+                - 03-First Time Booked
+                - 04-Active
+                - 05-Churning
+                - 06-Inactive
+                - 07-Reactivated
 
       - name: has_been_booked_within_current_month
         data_type: boolean
@@ -1487,6 +1508,10 @@ models:
         data_type: boolean
         description: If the deal has had a booking created in the past 12 months.
 
+      - name: has_been_offboarded
+        data_type: boolean
+        description: If the deal has been cancelled or not.
+
   - name: int_mtd_deal_metrics
     description: |
       This model contains the historic information regarding the deals in an aggregated manner.