[CVE-2608] use formData fullName for statement of truth signature

[andresriveratoro]

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

Switch PreSubmitInfo2 to source the expected signature name from formData.fullName instead of the user profile, removing the unused user prop and updating tests accordingly.

Related issue(s)

• https://va.ghe.com/software/va-cve/issues/2608

Testing done

Updated unit tests to drop the buildUser helper and user prop from renders, supplied fullName via formData, and renamed the signature-match assertions to reference the expected name rather than the profile name.

Screenshots

N/A

What areas of the site does it impact?

COE form behind feature flag

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