Fix N+1 on household reminders query

[gigxz]

Merging this PR

• use the squash-merge strategy for PRs targeting a release-X branch
• use a merge-commit or rebase strategy for PRs targeting the stable branch

Description

Issue: https://github.com/open-path/Green-River/issues/6980

Fix perf issue that was surfaced in sentry in QA.

Add data loading and regression test. The frontend loads the intake/exit assessment for each enrollment with a reminder.

It could probably be improved so that the relevant assessment (if any) is loaded directly on the reminder. But this change fixes the performance problem while preserving the existing api.

Type of change

Checklist before requesting review

• I have performed a self-review of my code
• I have run the code that is being changed under ideal conditions, and it doesn't fail
• If adding a new endpoint / exposing data in a new way, I have:
  • ensured the API can't leak data from other data sources
  • ensured this does not introduce N+1s
  • ensured permissions and visibility checks are performed in the right places
• Any major architectural changes are supported by an approved ADR (Architectural Decision Record)
• I have updated the documentation (or not applicable)
• I have added spec tests (or not applicable)
• I have provided testing instructions in this PR or the related issue (or not applicable)

//: # NOTE: system tests may fail if there is no branch on the hmis-frontend that matches the Source or Target branch of this PR. This is expected

[ttoomey]

looks great, thanks!