Improve YAML schema to get notion of version availability

[cderv]

From a discussion with @dragonstyle

general thoughts : maybe we should have a dev version (or pre-release version) of the reference pages ? (probably more realistic than a dev version of the all doc).

It would be very nice to have something like this (or perhaps even a version in the YAML schema that we can use to denote when a property become supported or ceased being supported). That would make it easy to generate version specific reference or a global reference that contains release information about availability... We still don't really have a great / consistent approach to documentation versions.

Originally posted by @dragonstyle in #2718 (comment)

Opening this to track the idea.

[cscheid]

I definitely agree. We already do version checking for extensions; we should do something similar for YAML properties.

There are a few things that need designing, though. Generally speaking, we want to store the information in the YAML schemas themselves. But the schemas are hierarchical, and can refer to one another. How do we decide what's the "valid" version range for a schema? Is it the narrowest or broadest? Where exactly do we signal this error?

[mcanouil]

For reference, there is now a "prelease" version of the documenation:

• https://prerelease.quarto.org/