Fix/att event multi calendars

[ryanaguilar]

Description & motivation

This PR addresses an edge case that occured in the BPS Stadium implementation where a student had multiple enrollments associated with different calendars per enrollment, which resulted in a student's attendance event not contributing to their attendance count.

Currently, the attendance_event_date is converted into a k_calendar_date by joining to fct_student_school_association and deduping by selecting enrollments where is_latest_annual_entry is true.

This updated model would instead join so that the attendance_event_date is within the range of the enrollment's entry_date and exit_withdraw_date (and accounts for null exit_withdraw_dates).

However, if a student has overlapping enrollments at the same school, multiple rows will
be returned for each date, and so an additional deduplication step is introduced.

See the original Monday item here.

Breaking changes introduced by this PR:

No breaking changes, but in rare cases could change attendance count.

PR Merge Priority:

• Medium

Changes to existing files:

New files created:

Tests and QC done:

Future ToDos & Questions:

• Further discussion may be needed on how to pick a winner when there overlapping enrollments with multiple calendars at the same school. The rule implemented here is one option that was presented during planning.

edu_wh PR Review Checklist:

Make sure the following have been completed before approving this PR:

• Description of changes has been added to Unreleased section of CHANGELOG.md. Add under ## New Features for features, etc.
• If a new configuration xwalk was added:
  • The code is written such that the xwalk is optional (preferred), and this behavior was tested, OR
  • The code is written such that the xwalk is required, and the required xwalk is added to edu_project_template, and this PR is flagged as breaking change (not for patch release)
  • A description for the new xwalk has been added to EDU documentation site here
• If a new configuration variable was added:
  • The code is written such that the variable is optional (preferred), and this behavior was tested, OR
  • The code is written such that the variable is required, and a default value was added to edu_project_template, and this PR is flagged as breaking change (not for patch release)
  • A description for the new variable has been added to EDU documentation site here
• Reviewer confirms the grain of all tables are unchanged, OR any changes are expected, communicated, and this PR is flagged as a breaking change (not for patch release)

[rlittle08]

any specific to use getdate() (returns a timestamp) instead of current_date() (returns a datestamp) here?

[ryanaguilar]

No specific reason, I don't think I realized there was a difference.

[rlittle08]

I don't think it affects the logic in this case, but I prefer current_date(), since the extra precision isn't needed and current_date() is available in databricks

[rlittle08]

I tested and deeply qc'd in Boston, TX, SC. Only changes were expected improvements. LGTM