Fix cache issues after updates

[rkg-mm]

Current Behavior

After Dtrack server updates, users regularly report a broken UI. I've seen it myself, in slack as well as requests from my collegues.
Even though the JS/CSS files seem to have mechanisms to enforce refreshed loading after updates due to changes in the numbers of the files (which should be double checked), the issue is that the HTML files are cached themselves, thus serving old HTML content and therefore pointing to outdated JS/CSS files, too.

Ideally, caching should be disabled for HTML files (following headers), and only be enabled for other file types.

Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: 0

(see also https://fred-gu.medium.com/fix-the-annoying-web-page-caching-issue-permanently-5d16527d0b5a)

Furthermore I see a risk in caching /config.json, which might lead to unexpected results after some config changes. This possibly should also not be cached.

Steps to Reproduce

1. Open UI in browser. If using Dev tools, ensure "disable caching" is not enabled.
2. Update from 4.10 to 4.11
3. Open UI in browser again without hitting F5 (which sometimes avoids cache)
4. With a high chance you end up with a broken UI in some places

Expected Behavior

After an update the HTML page should not be loaded from cache enforcing an update of all other files as well, and the UI should not be broken.

It should be double checked if the JS/CSS files are enforced to reload after HTML updates as I expect it due to the attached chunk numbers.

/config.json should be considered to be excluded from cache, too.

Dependency-Track Frontend Version

4.10.x

Browser

Google Chrome

Browser Version

No response

Operating System

Windows

Checklist

• I have read and understand the contributing guidelines
• I have checked the existing issues for whether this defect was already reported