Add cache-control records to served files, particularly contrib ui node .m

### Description

The .umd.js files for contributed ui nodes are served with no cache-control records. This means that it is up to the browser and/or intervening caching servers to decide whether and for how long to cache them, which can be problematic when a node is updated. The same may also be true for the core dashboard files, I don't know.

I am not an expert in this area, but I think the files should possibly be served with cache-control `public,max-age=0`.

See forum post https://discourse.nodered.org/t/is-there-an-issue-with-cache-headers-for-umd-js-file-in-contributed-d2-ui-nodes/88123 for discussion.

### Have you provided an initial effort estimate for this issue?

I am not a FlowFuse employee.