Add an explicit no-cache directive to returned headers

[MaryHirsch]

Expected Behaviour

Fabrica users are always running latest version of Fabrica

Current Behaviour

Cache causes problems for some end users:

1. set password doesn't work
2. the max publication date 2021 in the Fabrica Form is still saved in the browsers of lots of users

Steps to Reproduce

See examples in Front tickets here: https://app.frontapp.com/inboxes/teammates/464315/assigned/open/22422200725/search/workspace/tag%3Acache/2242511963

Context (Environment)

Screenshots

Further details

Comments from Mike :

"In staging, the returned headers have cache-control with a max-age of 0 and must-revalidate, but the age returned is indicating that the page served is ~72h old. That's technically allowed, as long as the cache revalidates that the page hasn't changed before returning it to the client. We should perhaps add an explicit no-cache directive as well. It's possible some browsers might ignore the max-age=0 without no-cache being present which could potentially lead to this scenario"

Proposal

Hypothesis

Possible Implementation