[DD] Final steps for Dispute Debt groundwork

[Dr-Pongo]

Issue Description

vets-website and content-build PRs are in draft mode, waiting for the new contract to mark ready and get merged. What's currently in the vets-website branch is a pretty high level skeleton, all the pages and basic functionaility are laid out, and remaining FE work is ticketed in the epic (Digital Dispute (VBA) - FE/BE Development #96176). We followed the setup progress in VA.gov application generator, but noticed a few steps that we may still need to do in the more detailed Creating a new application documentation.

Note: Keep in mind PR merge order

PRs for reference

• vets-website
  [DD] Dispute Debt initial vets-website#33332

• vets-api for prefill
  [DD] Initial prefill for digital dispute vets-api#19545

• content-build
  Adding dispute debt to registry content-build#2393

• vets-json-schema
  Add schema for Dispute Debt vets-json-schema#961

• FE ticket most of the work was completed under
  [DD] Initial FE implementation  #97002

Tasks

• Update team docs once complete

Remaining tasks defined in Manual Setup

• 3. Add an entry to src/applications/registry.json in the content-build
  • PR has been generated, just noting we missed it initially
• 4. Add your new application to the vets-api source app middleware configuration
• 6. Update revproxy config to reflect the addition of your application so that internal links created via react-routerwill work properly.

Design and Front End sync on implementation of design

• Required
• Complete
• Not Required
  • Initial skeleton of work, we can sync with design after the bulk of the refinement work in this epic is complete

Acceptance Criteria

• All steps have been completed for creating a new application
• All PRs merged
• Team docs updated

Testing

• N/A if non development work
• Testing passed and documented in this ticket based off the "Then" statement in the description

Test procedures:
If additional testing steps or credentials to perform testing are needed list them here

Ticket Creation - Definition of Ready

Ticket requirements

• Description written
• Tasks defined
• Acceptance criteria written
• Testing defined
• Add Labels
• Assign Type
• Assign Priority (Normal = Medium)
• Assign Group(s)
• Assign to a Project
• Attach to an Parent Epic
• Estimate Points