[Meta] Set the invalid state for all fields in Core in the Accessibility Object Model (AOM) properly

Problem/Motivation

While reevaluating #2852874: [Meta] Set the required state for all fields in Core in the Accessibility Object Model (AOM) it turned out that some of the fields in core also have not properly set the invalid state for fields that failed the validation on a form submit and in consequence are not programmatically labeled as invalid (see invalid_data.mp4) The affected fields in the test with Safari and VoiceOver were:

1. Formatted long text
2. Formatted long text with summary
3. Date datetime
4. Date datetime range
5. Date timestamp
6. Comment

The fields in point 1,2, and 6 are not labeled and announced as invalid in Safari, Firefox and Edge with VoiceOver active. While the fields in point 3,4, and 5 are properly announced as invalid in Firefox, but not in Safari and Edge.

Steps to reproduce

• Create a content type
• Add all available fields and make each of them required
• Create a node of the newly created content type
• Enable your screenreader of choice and submit the form without entering anything so each field errors out

Proposed resolution

Validate all available fields in core in other screenreaders like for example Jaws, NVDA, or Orca and figure out if there are more problems in different set ups.
Create dedicated issues for each affected field type and make sure that the aria-invalid="true" attribute is getting added and the field is properly announced as invalid.

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet