#schema change

Thanks everyone for your patience, I'll note that I'm committing a partial version of what was in MR!75, so if you're using all the features of this MR/patch then you might want to stick with that until all the sub issues of ✨ [meta]Make XML output more configurable Active are in, and then upgrade to the version of VDE that has those in.

@joelpittet yeah, agreed, I think it should almost always be in there, but I don't want to break something random in someone's export, so I think I'll punt that change to ✨ Allow specifying the XML encoding property Active and maybe we can make it the default for new installs or something like that.

You happy with the code otherwise?

I recommend keeping encoding="UTF-8" in there — it ensures correct character decoding, avoids cross-platform inconsistencies, and even if XML parsers are required to assume UTF-8 by default, it’s still best practice to include it explicitly.