fix: various uptake and visual enhancements to address design QA

[jaredcwhite]

Issue Overview

This PR addresses #3985

• This change addresses the issue in full
• This change addresses only certain aspects of the issue
• This change is a dependency for another issue
• This change has a dependency from another issue

Description

This PR includes changes/fixes to the household members portion and the Review summary portion of Common App to align with Seeds and maintain a consistent visual apperance.

How Can This Be Tested/Reviewed?

You can go to a listing here: https://deploy-preview-4038--bloom-exygy-dev.netlify.app/listing/f0ea701c-e488-45aa-ad48-ec73ab4e757a/testing_paper_67_montezuma_st_san_francisco_ca
and then fill out an application.

Checklist:

• My code follows the style guidelines of this project
• I have added QA notes to the issue with applicable URLs
• I have performed a self-review of my own code
• I have reviewed the changes in a desktop view
• I have reviewed the changes in a mobile view
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have assigned reviewers
• I have run yarn generate:client and/or created a migration if I made backend changes that require them
• My commit message(s) is/are polished, and any breaking changes are indicated in the message and are well-described
• Commits made across packages purposefully have the same commit message/version change, else are separated into different commits

Reviewer Notes:

Steps to review a PR:

• Read and understand the issue, and ensure the author has added QA notes
• Review the code itself from a style point of view
• Pull the changes down locally and test that the acceptance criteria is met
• Also review the acceptance criteria on the Netlify deploy preview (noting that these do not yet include any backend changes made in the PR)
• Either explicitly ask a clarifying question, request changes, or approve the PR if there are small remaining changes but the PR is otherwise good to go

On Merge:

If you have one commit and message, squash. If you need each message to be applied, rebase and merge.

[netlify]

✅ Deploy Preview for bloom-exygy-dev ready!

Name	Link
🔨 Latest commit	1509e04
🔍 Latest deploy log	https://app.netlify.com/sites/bloom-exygy-dev/deploys/664259a705ba12000891d468
😎 Deploy Preview	https://deploy-preview-4038--bloom-exygy-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[emilyjablonski]

I'm not seeing the values from the Figma reflected here, looking at the two notes on the side about the spacing between sections and between the label and value for example. I'm seeing the same w the notes for the summary page.

[jaredcwhite]

@emilyjablonski I thought I had gone through Figma and pulled out the right spacing values, but I'll go double-check.

[jaredcwhite]

@emilyjablonski I made a few updates based on your feedback and I think it's closer now. In cases where there seemed to be a discrepancy between the token name in Figma and what looks most identical in code practice, I went with what looked accurate.

[slowbot]

LGTM