Add single field component types vertical slice

[jimmoffet]

Overview

As a , I would like , so that I can _.

Context

REFERENCE: USWDS components for address, dob, email, gender, name, phone, pronouns, etc... are here: https://designsystem.digital.gov/patterns/create-a-user-profile/

Missing components:

NEEDS DESIGN & SCOPING:

• [ ] (Table input / component that allows member of the public to create and add multiple instances of a form-builder-defined pattern (see dependents on page 7, activities on page 9, school and license types on page 10, multiple addresses on page 11, job history on page 12, struggles with drugs page 13, financial info page 14) we may need to handle overflow items by attaching supplementary page. Hooking up th first N text inputs to the pdf and the remainder to the supplementary page will take some finesse
• [ ] Signature (need to discuss with pardon)

READY:

• [ ] Date
• [ ] email
• [ ] phone
• [ ] Social Security number
• [ ] Long text (or provide functionality for text input to expand as user types and elegantly handle max chars reached, maybe uswds has this)
• [ ] Gender

Acceptance Criteria

Required outcomes of the story

• [ ]

Research Questions

• Optional: Any initial questions for research

Tasks

Research, design, and engineering work needed to complete the story.

• [ ]

Definition of done

The "definition of done" ensures our quality standards are met with each bit of user-facing behavior we add. Everything that can be done incrementally should be done incrementally, while the context and details are fresh. If it’s inefficient or “hard” to do so, the team should figure out why and add OPEX/DEVEX backlog items to make it easier and more efficient.

• [ ] Behavior
  • [ ] Acceptance criteria met
  • [ ] Implementation matches design decisions
• [ ] Documentation
  • [ ] ADRs (/documents/adr folder)
  • [ ] Relevant README.md(s)
• [ ] Code quality
  • [ ] Code refactored for clarity and no design/technical debt
  • [ ] Adhere to separation of concerns; code is not tightly coupled, especially to 3rd party dependencies; dependency rule followed
  • [ ] Code is reviewed by team member
  • [ ] Code quality checks passed
• [ ] Security and privacy
  • [ ] Automated security and privacy gates passed
• [ ] Testing tasks completed
  • [ ] Automated tests pass
  • [ ] Unit test coverage of our code >= 90%
• [ ] Build and deploy
  • [ ] Build process updated
  • [ ] API(s) are versioned
  • [ ] Feature toggles created and/or deleted. Document the feature toggle
  • [ ] Source code is merged to the main branch

Decisions

• Optional: Any decisions we've made while working on this story

[JennyRichards-Flexion]

Ethan has a good instructive PR that was discussed in the last dev coffee - all the files that need to be touched are discussed there. Might be a good straightforward introduction.