Better Handling Dataset Page Cache At Frontend

Our gateway will, by default, cache most responses unless the frontend explicitly requests to turn it off:

For performance consideration, we cache most of the dataset pages by default.

As the user's visibility might change while the role changes, the cache could sometimes create confusion.

Although the user can turn off the gateway cache at deployment time via helm chart config, it would be better if we could:

Still keep the cache for most UI modules where the cache is appropriate for public (anonymous) users
The frontend should always request no-cache responses for non-anonymous users

magda-io / magda