Page duplicate dialog: don't require toggles

[distantnative]

Fixes #6921

Description

Summary of changes

• Page duplicate dialog: don't require toggles

Reasoning

• With required toggles, in v5 one cannot submit the form without activating the toggle, so false is no option.
• Apparently, in v4 toggles could be on or off even when required.
• I was wondering if we should change the general behavior for toggles (I assume also checkbox) to be the same as v4, but then required: true actually has no effect. So I do like that one can actually require a toggle/checkbox to be set. We just have to remove the required option from use cases like here where it's not right.

Changelog

Not from this PR, but so far missed...

Breaking changes

• required: true on checkbox and toggle fields now enforces that these fields need to be checked/toggles (active state)

Ready?

• In-code documentation (wherever needed)
• Unit tests for fixed bug/feature
• Tests and CI checks all pass

For review team

• Add lab and/or sandbox examples (wherever helpful)
• Add changes & docs to release notes draft in Notion

[afbora]

IMHO v5 behavior is correct. Otherwise required attribute would useless. But this is also a breaking change. If we continue with that we need to add to breaking changes in release notes.

Another way is deprecate this usage in v5 and remove it in v6.

Also PR is looks good to me and work great! 👍

[bastianallgeier]

I agree that the new behavior makes a lot more sense. There's an indeterminate state for checkboxes: https://css-tricks.com/indeterminate-checkboxes/ but we don't support that yet at all. I think this would be the only way to have toggles and checkboxes that are not set yet. But with our current state, the required attribute does not make any sense in v4