My VA - forms status post-launch cleanup

Are you removing, renaming or moving a folder in this PR?

[x] 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

:warning: TeamSites :warning:

Examples of a TeamSite: https://va.gov/health and https://benefits.va.gov/benefits/. This scenario is also referred to as the "injected" header and footer. You can reach out in the #sitewide-public-websites Slack channel for questions.

Did you change site-wide styles, platform utilities or other infrastructure?

[x] No
[ ] Yes, and I used the proxy-rewrite steps to test the injected header scenario

Summary

This PR

removes all instances of myVaFormSubmissionStatuses feature toggle on FE
deletes ApplicationInProgress component (old component for in-progress forms)

Related issue(s)

Testing done

all unit and e2e tests still pass

What areas of the site does it impact?

My VA - Benefit applications and other forms

Acceptance criteria

[ ] all instances of myVaFormSubmissionStatuses/my_va_form_submission_statuses are removed
no regression errors

Quality Assurance & Testing

[ ] I fixed|updated|added unit tests and integration tests for each feature (if applicable).
[x] No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
[x] 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

[x] 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

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

department-of-veterans-affairs / vets-website

My VA - forms status post-launch cleanup #33081