VAGOV-TEAM-96557: Default paragraphs

[ryguyk]

Description

This adds a "Your personal information" chapter to a Digital Form when the form is first created using Form Builder UI. The chapter includes two sub-chapters ("Name and date of birth" and "Identification information").

Closes department-of-veterans-affairs/va.gov-team#96557

Testing done

• Functional test updated. Confirms that default paragraph with sub-paragraphs exists after initial node creation.
• Manually tested as well.

Screenshots

Admin view after creating form in Form Builder:

QA steps

As ad admin:

1. Navigate to /form-builder/form-info.
   • Fill in form and click "Save and continue".
   • Validate that you are redirected to form-builder/{nid}/layout.
2. On the Layout page.
   • Validate that the "Your personal information" step has "COMPLETE" status with green label.
   • Copy the nid value and manually navigate to /node/{nid}/edit.
3. On the default/admin node-edit page:
   • Validate that the form has a "Your personal information" chapter.
   • Validate that the chapter contains two sub-chapters:
     • "Name and date of birth"
     • "Identification information"

Definition of Done

• Documentation has been updated, if applicable.
• [ x Tests have been added if necessary.
• Automated tests have passed.
• Code Quality Tests have passed.
• Acceptance Criteria in related issue are met.
• Manual Code Review Approved.
• If there are field changes, front end output has been thoroughly checked.

Select Team for PR review

• CMS Team
• Public websites
• Facilities
• User support
• Accelerated Publishing
• Form Engine

Is this PR blocked by another PR?

• DO NOT MERGE

Does this PR need review from a Product Owner

• Needs PO review

CMS user-facing announcement

Is an announcement needed to let editors know of this change?

• Yes, and it's written in issue ____ and queued for publication.
  • Merge and ping the UX writer so they are ready to publish after deployment
• Yes, but it hasn't yet been written
  • Don't merge yet -- ping the UX writer to write and queue content
• No announcement is needed for this code change.
  • Merge & carry on unburdened by announcements

[github-actions]

Checking composer.lock changes...