Merged PR 2498: Materialise int_dates_mtd and int_dates_by_deal as table to improve performance

# Description

Materialise int_dates_mtd and int_dates_by_deal as tables. This should improve the run speed as seen in local by quite a bit, and hopefully provide a better starting point for adding new dimensionality on business kpis.

I also documented these 2 models, that were missing :)

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

models/intermediate/cross/int_dates_mtd.sql

@@ -1,17 +1,6 @@
-/*
-This model provides Month-To-Date (MTD) necessary dates for MTD-based models to work.
-- For month-to-month complete information, it retrieves all end month dates that have elapsed since 2020.
-- For month-to-date information, it retrieves the days of the current month of this year up to yesterday. 
-  Additionally, it also gets the days of its equivalent month from last year previous the current day of month of today.
 
-Example:
-Imagine we have are at 4th June 2024.
-- We will get the dates for 1st, 2nd, 3rd of June 2024.
-- We will also get the dates for 1st, 2nd, 3rd of June 2023.
-- We will get all end of months from 2020 to yesterday, 
-  i.e., 31st January 2020, 29th February 2020, ..., 30th April 2024, 31st May 2024.
+{{ config(materialized="table", unique_key="date") }}
 
-*/
 with
     int_dates as (select * from {{ ref("int_dates") }} where date_day >= {{ var("start_date") }}),
     raw_dates as (