103996 - Update custom signature validator to account for whitespace - form 10-7959c

[michaelclement]

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

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

This PR fixes a bug with the custom signature validator in form 10-7959c. Previously, if any of the name fields included whitespace, the validator would not strip the whitespace out which led to confusing error messages if a user had, for example, a double-name like "John David".

Related issue(s)

• Fix signature whitespace bug in OHI va.gov-team#103996

Testing done

• Manual
• Unit

Screenshots

	Before	After
Desktop

What areas of the site does it impact?

IVC CHAMPVA form 10-7959c only

Acceptance criteria

Quality Assurance & Testing

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Linting warnings have been addressed
• Documentation has been updated (link to documentation *if necessary)
• Screenshot of the developed feature is added
• Accessibility testing has been performed

Error Handling

• Browser console contains no warnings or errors.
• Events are being sent to the appropriate logging solution
• Feature/bug has a monitor built into Datadog or Grafana (if applicable)

Authentication

• Did you login to a local build and verify all authenticated routes work as expected with a test user

Requested Feedback

NA

[michaelclement]

Previously, the function ran replaceAll(' ', '') on the signatureNamevalue, but not on the actualapplicantName` property. Now it is consistent across both values so the comparison is accurate.