CH36 Form Name Changes (25 to 27)

[steele-lm]

Issue Description

The PCPG form number was changed from 25-8832 to 27-8832. (It was changed in 2023 from 28 to 25 in #62663.)

Related sitewide content ticket to update static references.

Designs from previous form number update are here.

Redirect work is #78077

---

Tasks

• Update introduction page with new form number (27-8832).
• Update language in form subtitle to read: Equal to VA Form 27-8832, 28-8832, or 25-8832 (Educational/Vocational Counseling Application). Currently it reads:
  
• Update the in-progress form alert box to say: Please complete the 27-8832 form to apply for Personalized Career Planning and Guidance.
• Update Form Title to 27-8832. Currently it reads:
  
• Update breadcrumb to 27-8832. Currently it reads:
  

Acceptance Criteria

• All instances of 25-8832 have been changed to 27-8832 on CH36 intro page
• 25-8832 has been changed to 27-8832 on CH36 form subtitle
• 25-8832 has been changed to 27-8835 within in-progress form alert box
• 25-8832 has been changed to 27-8835 within breadcrumb

[zack]

Compiling information I received from @DLarson-Oddball and @jerekshoe here:

In order to complete this task, we're going to need to take a number of steps:

1. Create a new schema in vets-json-schema for the new application.
2. Create a copy of the application in vets-website. Don't forget to update the manifest.json file. I think this is where we'll want to update vets-website to point to the new vets-json-schema commit?
3. In content-build registry.json, create a new entry for the new application.
4. Deploy content-build and make sure everything's working correctly.
5. Somewhere around here we'll want to change all of the references in vets-website, but I'm not exactly sure when that needs to happen. There are lots of references outside of the application to the form name, like test files, links, etc. See the changes in the PR in the note at the bottom of this comment.
6. Submit a request to create a redirect so that anyone who goes to the old URL will be forwarded to the new URL. Make sure this works for in-progress forms.
   1. Note from Dakota: "We had issue with child pages not following the redirect initially, so it would be good to ensure child pages are covered as well when they roll out the second redirect."
7. The old application, schema, etc. can all be removed.

NOTE: There are still a large number of references to '28-8832' in the codebase and these will also need to be updated to the new for name '27-8832'. See a draft of this work here: department-of-veterans-affairs/vets-website#28545.