docs: version tags for examples

[J-Sek]

resolves #22645

• discuss: what minimal version do we want to show? v3.6.0 or v4.0.0

[MajesticPotatoe]

It make more sense to use a json file to track all this, and then incorporate the tag into the example.vue component. (we already do this on a component basis via new-in.json, so could just add it into their)

[J-Sek]

Would it meant we rely on the example file names to include the exact name after initial prefix? The prop is dumb/simple and could end up with lower mental overhead in comparison to some magic resolver. API docs are more strict and it makes sense there. Curious what others would think.

[MajesticPotatoe]

Name is already available in example component (because it uses it to get the actual example file) so a lookup into the json should also be simple.

Was more for consistency with what already is done, and to increase flexibility/usability (eg if you want to use that information elsewhere, such as a page that lists all of the new components by version).

could be as simple as

{
  "Examples": {
    "v-avatar/prop-size": "3.4.0",
    // or
    "v-avatar": {
      "prop-size": "3.4.0"
    }
  }
}

or add on the the existing structure

{
  "VAvatar": {
    "props": {
      "text": "3.4.0",
    },
    "examples": {
      "prop-size": "3.4.0"
    }
  }
}