EVSS PCIU Migration: Step 6d: DISCOVERY for vets-website PCIU removal

[RachalCassity]

CREATE DRAFT PR - CANNOT MERGE UNTIL Contact information V2 is successfully enabled in production

User Story

As a developer, I want to remove all references of PCIU to ensure VA.gov no longer uses PCIU, as we transition to VA Profile in preparation for the PCIU deprecation.

Issue Description

We're currently uncertain about the level of frontend work required to remove PCIU from vets-website and the extent of external assistance needed. This ticket should outline the scope of work and specify any tasks that require Platform's involvement in #99359 and, if deemed necessary, write up any tickets for work needed for other teams.

Tasks

• Evaluate what will need to be done to remove PCIU on the frontend (create discovery doc if necessary).
• Evaluate if the above will cause any breaking changes (Consult with a FE engineer if necessary)
• Write up Platform tasks in PCIU Migration: Step 6g: vets-website PCIU removal #99359
• Create other tickets for additional work, if necessary. A skeleton ticket for the Vets Website removal has been created here
• Communicate findings to team (+ FE team if necessary)

Acceptance Criteria

• Create a discovery doc, clearly outlining the specified findings and tasks
• PCIU Migration: Step 6g: vets-website PCIU removal #99359 is updated with tasks
• Other tickets are created and linked to the epic.

---

Validation

Assignee to add steps to this section. List the actions that need to be taken to confirm this issue is complete. Include any necessary links or context. State the expected outcome.

[AshleyGuerrant]

Moving out 2 sprints. This work should happen after ContactInformation is complete. ContactInformation is replacing PCIU, these tickets cannot be worked on until ContactInformation has been done and the PCIU has been replaced.

[RachalCassity]

Contact Information V2 has to replace PCIU in prod before PCIU references can be removed.