feat: Browser side Azure static assets caching

[cooper667]

Description

By default, CKAN caches badly The settings it give us for caching are fairly blunt, but we can set some things at the CDN level. It sets must-revalidate on things, which according to the spec:

The must-revalidate directive ought to be used by servers if and only if failure to validate a request could cause incorrect operation, such as a silently unexecuted financial transaction.

And no-cache, which doesn't technically mean don't cache, but apparently some browsers DO interpret it as that

The no-cache response directive, in its unqualified form (without an argument), indicates that the response MUST NOT be used to satisfy any other request without forwarding it for validation and receiving a successful response

So we probably don't need that on...fonts etc.

This PR allows static assets to be cached browser side. This helps a lot when navigating pages and generally using the site as it makes the user experience quicker and removes some load from the server. We cache for a long time, and invalidation is handled by hashes in the names of the assets (we may want to consider how we handle images if we have some that change frequently)

The list of extensions cached is:

js
css
woff
svg
jpg
woff2

We likely want to do similar with AWS/Cloudflare

The next step is caching in our CDNs too to help first load on these requests, this requires some CKAN config tho.

Testing (delete if not applicable)

Deployed on AfroStaging

Checklist

Put an x in the boxes that apply to this pull request (you can also fill these out after opening the pull request).
You may not need to check all boxes.

• The GitHub ticket for this issue has been updated to "Ready to Review" or equivalent.
• I have developed these changes in discussion with the appropriate project manager.
• My code follows the general Fjelltopp documentation (see Confluence).
• I have made corresponding changes to the Fjelltopp documentation (see Confluence).
• I have rebased this branch with master.
• New dependency changes have been committed.
• I have added automated tests that prove my fix is effective or that my feature works.
• New and existing tests pass locally with my changes.
• My changes generate no new warnings.
• I have performed a self-review of my own code.
• I have assigned at least one reviewer.
• I have assigned at least one label to this PR: "patch", "minor", "major".

[ChasNelson1990]

We've used staging a lot to test the WAF and nothing seems broken!

[github-actions]

🚀 [bumpr] Bumped! New version:v3.3.0 Changes:v3.2.0...v3.3.0