Merged PR 3047: Override migration date with join date if join date is after migration date

# Description

Quick fix to make lower_limit_migration_date_utc more robust for new dash reporting purposes. I noticed some cases in which users were actually created after the migration date. In these cases, I just keep joined date.

# 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.
- [ ] 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.

Related work items: #22331

models/intermediate/core/schema.yml

@@ -2528,6 +2528,17 @@ models:
           this date.
         tests:
           - not_null
+      - name: claim_enforcement_priority
+        data_type: integer
+        description: |
+          Informative field. It just states which claim enforcement priority 
+          has been used for the computation.
+      - name: is_overridden_with_joined_date
+        data_type: boolean
+        description: |
+          Informative field. Boolean to indicate if the expected migration date 
+          based in the logic is finally overridden with the user joined date 
+          in case the user was created after the expected migration date.
 
   - name: int_core__address_validations
     description: