Add how to correctly get cached purged version to template source (the .json)

[LittleEndu]

There are many ways the script could do cache busting, but it seems sometimes it actually works against our best wishes. Real solution to this should be investigated, and if there's a way to fix it it should be added into the .json so that after loading it for the first time the script knows how to refresh it correctly.

This could also just include an incremental version number i.e filename part of the path is the cache bust not the uri query. For example templateManager is told to add https://littleendu.xyz/template.json as a source, and then in the .json templateManager would find "hey, we actually have updated this 45 times. You can find the templates in https://littleendu.xyz/template-v45.json and in the future, try https://littleendu.xyz/template-v46.json to see if we have an update"

[april83c]

Regarding the version number in filename, I think the JSON should be able to specify whether this should be enabled or not (i.e. it's decided on the first time it gets the JSON)

Also, for our own templates (and HYTC): I should check what cache headers are being sent to the client — maybe I can make it not cache the JSON?

[LittleEndu]

I think the JSON should be able to specify whether this should be enabled or not

That's the title part of this issue 😛

Like a new key in the .json root named version residing here:

templateManager/src/template.ts

Lines 27 to 34 in d99ae00

	export interface JsonParams {
	contact: string | undefined
	contactInfo: string | undefined // alias for contact
	templates: TemplateParams[]
	notifications: string | undefined // url to broadcaster
	whitelist: NamedURL[]
	blacklist: NamedURL[]
	}