Fix (forms): Add contact info fields to certificate forms

[sajclarke]

Description

This PR enhances the birth and marriage certificate request forms by adding missing contact information fields and improving form structure. The birth certificate form is restructured to include new sections for parent details and order information with payment integration, while the marriage certificate form receives contact fields and a nationality verification question.

Type of Change

• Bug fix
• New feature
• Documentation update

Changes Made

Get Birth Certificate Form

• Add email field (required) to applicant
• Add telephoneNumber field (required) to applicant

Get Marriage Certificate Form

• Update label capitalization ("Address Line 1" → "Address line 1", "Address Line 2" → "Address line 2")
• Add email field (required) to applicant
• Add telephoneNumber field (required) to applicant
• Add isBarbadosNational field (required) with yes/no validation

Files Changed

• schemas/get-birth-certificate.json - Complete schema restructuring with new sections (540 insertions, 514 deletions)
• schemas/get-marriage-certificate.json - Added contact fields and nationality verification (26 changes)

Notes

The birth certificate form now includes payment integration and parent detail capture, significantly expanding its functionality. Both forms now require contact information (email and phone) and verify applicant nationality. The restructuring uses nested objects for better data organization and field management.

Testing

• Birth certificate form validates all new required fields
• Marriage certificate form validates email and phone fields
• Payment processor integrates correctly with EZPay
• Email template renders with new nested field paths
• Parent detail fields work as optional nested objects
• Order quantity validation enforces 1-10 copies
• Nationality validation accepts yes/no options
• Form submission tested end-to-end
• Responsive design verified across device sizes

Related Github Issue(s)/Trello Ticket(s)

Checklist

• Code follows project style guidelines
• Self-review completed
• Tests added/updated for new form sections
• Documentation updated with new field structure
• Payment integration verified
• Email template expressions updated
• Database migration plan documented if needed

[amazon-inspector-n-virginia]

⏳ I'm reviewing this pull request for security vulnerabilities and code quality issues. I'll provide an update when I'm done

[amazon-inspector-n-virginia]

✅ I finished the code review, and didn't find any security or code quality issues.