feat(input_schema): datepicker dateType property

[mfori]

This PR replace allowAbsolute/allowRelative boolean properties for datepicker with single dateType property that accepts values absolute, relative and absoluteOrRelative based on:

• docs: add datepicker dateType property to input schema apify-docs#1227
• https://apify.slack.com/archives/C010Q0FBYG3/p1730210649660309?thread_ts=1728907212.870409&cid=C010Q0FBYG3

dateType property:

• is optional
• is valid only when editor is datepicker
• is only for ui input representation, no validation is executed based on this property

[gippy]

This is to force it to just a single value?

[mfori]

It's already after the

"if": {
    properties": {
        "isSecret": {
            "not": {
                "const": true
             }
         }
    }
},

So there can't be any other boolean value then false. It's not necessary but I like it in the same way I did with:

"editor": { "enum": ["datepicker"] },

[fnesveda]

As I understand this, this is a breaking change, because suddenly the input schemas with the old allowAbsolute etc. properties will be invalid. Just to be sure, is that OK? Were they not documented anywhere yet? Are there no Actors with input schemas containing those properties?

Otherwise looks good.

[mfori]

As I understand this, this is a breaking change, because suddenly the input schemas with the old allowAbsolute etc. properties will be invalid. Just to be sure, is that OK? Were they not documented anywhere yet? Are there no Actors with input schemas containing those properties?

Otherwise looks good.

Yes, these old values allowAbsolute and allowRelative were never documented anywhere and are not used by any Actors. The documentation for this new property is ready here: apify/apify-docs#1227