[Eng] Update UI for Form Structure components

[nichole-aquino]

Overview

Form builders can easily add/edit Form Structure components (question set, repeating question set)

Context

Reference:

• Design ticket: [Design] Update UI for Form Structure components #430
• Figma mockups
• USWDS components: text input and text-area, unstyled button

Rename components:

• Fieldset: Change to Question set
• Repeater: Change to Repeating question set

On the build screen, for the heading:

• Relabel the input field to ‘Question set label’
• For the repeating question set, add option to edit the button text
• Add optional help text component; the field grows as needed (GH ticket #373)
• Add optional information box component 'Add supplementary information or instructions'(GH ticket #415)

On the build screen, for the ‘Add question to fieldset’ link

• Replace grey link with unstyled button
• Replace copy to ‘Add question to set’

Acceptance Criteria

The changes should be made to the following question types:

• Question set (aka field set)

• Repeating question set (aka repeater)

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