ValueOnly: Support dateTime Range and not only string

[BirgitBoss]

Is your feature request related to a problem? Please describe.
see https://github.com/admin-shell-io/aas-specs-api/pull/222/files#r1653646603

In case of date range it could help to be more precise and define a DateValue:

DateValue: 
  type: string
  format: date-time

Without that every date format could be used and would be be not interoperable.

[BirgitBoss]

2024-12-11 TF Metamodel

i.e. it is proposed to extend

"RangeValueType": {
      "oneOf": [
        {
          "$ref": "#/definitions/StringValue"
        },
        {
          "$ref": "#/definitions/NumberValue"
        },
        {
          "$ref": "#/definitions/BooleanValue"
        }
      ]
    },

with

"RangeValueType": {
      "oneOf": [
        {
          "$ref": "#/definitions/StringValue"
        },
        {
          "$ref": "#/definitions/NumberValue"
        },
        {
          "$ref": "#/definitions/DateValue"
        },
        {
          "$ref": "#/definitions/BooleanValue"
        }
      ]
    },

    "NumberValue": {
      "type": "string",
      "additionalProperties": false,
     format: date-time
    },

format is supported for JSON schema 2020-12 (see https://json-schema.org/draft/2020-12/draft-bhutton-json-schema-validation-00#rfc.section.7) but not yet in 2019-09. Since we still use 2019-09 we can only introduce it as soon as we decide to switch to JSON schema 2020-12.

postpone this issue

still to be clarified: would this kind of change be backward compatible?