Merged PR 2604: Finished adding address_validation to reporting

# Description

Finished adding address_validation to reporting for check-in hero

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

models/reporting/core/core__vr_check_in_cover.sql

@@ -10,6 +10,8 @@ select
     is_past_check_in as is_past_check_in,
     is_awaiting_check_in as is_awaiting_check_in,
     cover_was_purchased as cover_was_purchased,
+    address_validation_passed as address_validation_passed,
+    address_validation_notes as address_validation_notes,
     cover_was_rejected as cover_was_rejected,
     guest_email as guest_email,
     last_name as last_name,

models/reporting/core/schema.yaml

@@ -244,6 +244,16 @@ models:
           This is identified by the fact that there is a payment of type 
           check-in cover associated with this guest journey.
 
+      - name: address_validation_passed
+        data_type: boolean
+        description: 
+          "Boolean to indicate if the validation was approved or not.
+          In case there was a problem with the validation it will be Null"
+
+      - name: address_validation_notes
+        data_type: character varying
+        description: "Notes in case there was some problem with the validation."
+
       - name: cover_was_rejected
         data_type: boolean
         description: |