Add character limits for Appoint a Representative

[rjohnson2011]

Are you removing, renaming or moving a folder in this PR?

• No, I'm not changing any folders (skip to TeamSites and delete the rest of this section)
• Yes, I'm removing, renaming or moving a folder

If the folder you changed contains a manifest.json, search for its entryName in the content-build registry.json (the entryName there will match).

If an entry for this folder exists in content-build and you are:

1. Deleting a folder:

   1. First search vets-website for all instances of the entryName in your manifest.json and remove them in a separate PR. Look particularly for references in src/applications/static-pages/static-pages-entry.js and src/platform/forms/constants.js. If you do not do this, other applications will break!
      • Add the link to your merged vets-website PR here
   2. Then, Delete the application entry in registry.json and merge that PR before this one
      • Add the link to your merged content-build PR here

2. Renaming or moving a folder: Update the entry in the registry.json, but do not merge it until your vets-website changes here are merged. The content-build PR must be merged immediately after your vets-website change is merged in to avoid CI errors with content-build (and Tugboat).

⚠️ TeamSites ⚠️

Examples of a TeamSite: https://va.gov/health and https://benefits.va.gov/benefits/. This scenario is also referred to as the "injected" header and footer. You can reach out in the #sitewide-public-websites Slack channel for questions.

Did you change site-wide styles, platform utilities or other infrastructure?

• No
• Yes, and I used the proxy-rewrite steps to test the injected header scenario

Summary

Implement character limits on the following pages and related fields, as follows:

/claimant-relationship

• 42 characters for the "Describe your relationship to the Veteran" open input

/claimant-personal-information

• 12 characters for the First Name
• 1 character for the Middle Initial
• 18 characters for the Last Name

/claimant-contact-mailing

• 30 characters for No. & Street (Street address)
• 5 characters for Apt./Unit Number (Street address line 2)
• 18 characters for City
• 2 characters for State/Province/Region
• 9 characters for Zip Code/Postal Code

/claimant-contact-phone-email

• 31 characters for Email address

/veteran-personal-information

• 12 characters for the First Name
• 1 character for the Middle Initial
• 18 characters for the Last Name

/veteran-contact-mailing

• 30 characters for No. & Street (Street address)
• 5 characters for Apt./Unit Number (Street address line 2)
• 18 characters for City
• 2 characters for State/Province/Region
• 9 characters for Zip Code/Postal Code

/veteran-contact-phone-email

• 61 characters for Email address

/veteran-identification

• 9 characters for Veteran's VA File Number
• 9 characters for Veteran's Service Number

Related issue(s)

Github Ticket

Testing done

• Additional max length specs for each attribute changed.

Screenshots

Following showcases the maxChars feature on the Frontend which disables any additional characters being input:

[cosu419]

Approved - eventually we will need to import these from vets-json-schema rather than declaring them in line here, but saving that for a later PR.