Fix time range filename casing again

[kriswest]

When we corrected the casing of timerange to timeRange in 2.1 the un-cased filename persisted in /website/static/next and will break links on case-sensitive filesystems. This PR repeats the two-step fix for that already applied in /schema/context and /website/static/2.1.

FYI the website is clearly served from a case insensitve filesystem as both of the following links work (and should continue to):

• https://fdc3.finos.org/schemas/next/context/timerange.schema.json
• https://fdc3.finos.org/schemas/next/context/timeRange.schema.json

[netlify[bot]]

✅ Deploy Preview for fdc3 ready!

Name	Link
🔨 Latest commit	23c687c2c4352187841e7b40adcc25bcfdb87fcf
🔍 Latest deploy log	https://app.netlify.com/sites/fdc3/deploys/672cc1ee0e86ac00084cb811
😎 Deploy Preview	https://deploy-preview-1420--fdc3.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.