feat: DAH-3550 Priorities Checkbox Group

[jtcaovan]

Description

Builds out the Priorities Checkbox group of fields component

Jira ticket

https://sfgovdt.jira.com/browse/DAH-3550

Before requesting eng review

Version Control

• branch name begins with angular if it contains updates to Angular code
• branch name contains the Jira ticket number
• PR name follows type: TICKET-NUMBER Description format, use DAH-000 if it does not need a ticket
• PR name follows urgent: Description format if it is urgent and does not need a ticket

Code quality

• the set of changes is small
• all automated code checks pass (linting, tests, coverage, etc.)
• if the PR is a bugfix, there are tests and logs around the bug

Code conventions

• web pages are formatted with .scss stylesheets and ui-seeds tokens, rather than inline styles or Tailwind

Review instructions

• instructions specify which environment(s) it applies to
• instructions work for PA testers
• instructions have already been performed at least once

Request eng review

• PR has needs review label
• Use Housing Eng group to automatically assign reviewers, and/or assign specific engineers
• If time sensitive, notify engineers in Slack

Before merging

Request product acceptance (PA) testing

• PA tested in the review environment (use needs product acceptance label)
• if PA testing cannot be done, changes are behind a feature flag

[jimlin-sfgov]

issue: the Salesforce back-end expects specific string values, e.g. 'Mobility impairments' instead of 'mobilityImpairment'. See here. I would suggest creating an array in the constants.tsx file and importing it into this file.

[jimlin-sfgov]

LGTM