Address browser caching issues with auth routes

[edmund-dunn]

User Story or Problem Statement

Right now, browser caching is turned on and set to 1 day. This is a blanket policy for all Drupal routes. There is an issue in the queue for Drupal Core: https://www.drupal.org/node/2352009. This is causing an issue with some of the authentication routes being cached, and authentication checks are receiving 403 errors because they are cached. The browser caching policy does not allow individual settings to bubble up and so eve if these routes are set to not be cached in the browser they are still cached.

Relevant Links for Context

• https://dsva.slack.com/archives/CDHBKAL9W/p1736180296859259
• https://vfs.atlassian.net/wiki/spaces/PCMS/pages/3739680788/Login+Issues+related+to+browser+cookies
• • Editors receiving warning about accepting cookies in the browser #20140

Steps for Implementation

We will need to test this over time, starting at 3 hours, and reduce the time that pages are cached in the browser one step at a time. While this is happening, we also need to watch the performance dashboard for potential impact on performance.

Since this only affects the browser cache, it will not affect JSON:API, GraphQL, or other APIs.

Acceptance Criteria

• CMS users are no longer getting the error message about the cookies in their browser.

[gracekretschmer-metrostar]

Help Desk's write up of the caching issue: https://vfs.atlassian.net/wiki/spaces/PCMS/pages/3739680788/Login+Issues+related+to+browser+cookies