FE: Remove Forms API Call on PDF Click Events

BLOCKER(s)

See https://github.com/department-of-veterans-affairs/va.gov-cms/issues/10562, the better approach may be to re-use the simpler javascript flow from the Form Search page

Description

This API call is unique to the download flow on Form Detail pages; the Form Search page doesn't have this extra API call.

During discovery performed under https://github.com/department-of-veterans-affairs/va.gov-cms/issues/10061, we identified a seemingly redundant Forms API call being made when a user clicks the Form PDF download link. This call is preventing directly serving of the Form PDF, and in some cases even preventing vets from accessing the PDF which, if directly visited, would download into the browser.

Current behavior exhibits UX concerns (user is left waiting while the API is called, for as long as that takes, with no visible indicator of what is happening). Contrast this behavior with one in which the user has javascript disabled: the user is always brought directly to the PDF asset--meaning those without javascript are MORE likely to actually get to the file, than those with javascript turned on.

This click event is triggered on Forms Detail pages when a user clicks the link under 'Downloadable PDF'. See steps 1-4 in the below image:

VACMS-10061 - Discovery Form FE Workflow.png

Acceptance Criteria

[ ] Fully grok the entirety of the Mural created in #10061 for context of the extra API call (LINK TBD)
[ ] Validate that it's a good idea to remove this API call
[ ] Ensure robust testing in a lower env (Staging) – Flipper
[ ] Remove the call
[ ] Ensure robust testing in a lower env (Staging) – Flipper
[ ] QA against relevant use cases

CMS Team

Please check the team(s) that will do this work.

[ ] Program
[ ] Platform CMS Team
[ ] Sitewide Crew
[ ] ⭐️ Sitewide CMS
[x] ⭐️ Public Websites
[ ] ⭐️ Facilities
[ ] ⭐️ User support

department-of-veterans-affairs / va.gov-cms