Merged PR 4121: PMS in new dash reporting

# Description

PMS in new dash reporting

# 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.
- [ ] I've picked the right materialization for the affected models.

# Other

- [ ] Check if a full-refresh is required after this PR is merged.

PMS in new dash reporting

Related work items: #26589

models/reporting/core/core__new_dash_user_overview.sql

@@ -8,6 +8,8 @@ select
     has_user_moved_from_old_dash as has_user_moved_from_old_dash,
     user_migration_phase as user_migration_phase,
     user_estimated_migration_date_utc as user_estimated_migration_date_utc,
+    has_active_pms as has_active_pms,
+    active_pms_list as active_pms_list,
     company_name as company_name,
     first_name as first_name,
     last_name as last_name,

models/reporting/core/schema.yml

@@ -1158,6 +1158,19 @@ models:
         data_tests:
           - not_null
 
+      - name: has_active_pms
+        data_type: boolean
+        description: |
+          Does the host have an active associated PMS.
+        data_tests:
+          - not_null
+
+      - name: active_pms_list
+        data_type: string
+        description: |
+          Name of the active PMS associated with the host. It can have more than
+          one PMS associated with it. It can be null if it doesn't have any PMS associated.
+
       - name: company_name
         data_type: string
         description: |