Identify caching issue for editor-ui

[conorriches]

When deploying custom instructions work to staging, the team noticed that some were getting the latest code (Lois, Adrian, Jamie), but others were seeing the old code (Mel, Laura, Conor)
This still occurred after clearing the browser cache and changing browsers, suggesting it is a caching issue on the server side.
It appears to fix itself after an unknown time.

Conor's thoughts

• there's a cache somewhere that means there's a delay after deploying
• It could be in AWS; an initial look at Cloudflare didn't reveal anything

Potential steps to created

• deploy code from editor-ui to staging
• clear browser cache
• The old code is still shown.

Output

• Find a fix for how to clear cache on new deployments.
• OR provide details on the caching levels and how long they cache for.

[create-issue-branch]

Branch issues/1181-Identify_caching_issue_for_editor-ui created!