Update CKEditor 5 to 35.3.2 to fix voice control/IME on some platforms

So we have to decide if this stable-blocks CKEditor 5, thus not allowing it to be stable in the D10 beta

Because I've worked so closely with Drupal's CKEditor 5 integration, it would be ideal if another accessibility maintainer could provide a recommendation. I have my own thoughts on how to address, but I'd like to yield to anyone that isn't influenced by many months working on this.

Some highlights to consider

• No dictation / IME support is bad, and the CKEditor 5 team agrees it's bad. It's a high priority to address and significant progress has already been made.
• As Wim mentioned above There is literally a branch with dictation/IME working great, with the exception of Android. There is a ( fallback that will allow Android to work if necessary. It's not ideal dev-cycle wise, but would fully accommodate the user. The CKEditor 5 team said they'd resort to that option if they couldn't get the preferred approach working, and that would be released mid December at the latest.
• There is a workaround that's not ideal but makes dictation/IME possible: create the content in another app/field and paste it into CKEditor 5

With the above in mind, is it acceptable to mark the CKEditor 5 as stable before the Beta release in early Sept, knowing that the Dictation / IME fix will not be ready by then, but is highly likely to exist before the D10 rc (+ knowing there is a workaround that makes dictation/IME work with some additioal effort)

Regarding this being a beta blocker: I spoke to @mgifford about this and his suggestion was one I like better than any of the options I'd thought of.

Given the following:

• Strong evidence suggesting dictation/IME will be fixed
• This is not a problem in CKEditor 4, and Ckeditor 4 will be available as a contrib module

It would be acceptable to mark this stable IF the CKSource agrees to continue supporting CKEditor 4 until the dictation/IME problems are addressed in CKEditor 5, even if this means having to delay EOL.

(I'd also add that I'd like to make the likely-to-be-fixed-soon dictation problem very evident in release notes, etc. so site owners can test their D10 sites with the CKEditor 4 module in case that becomes necessary.)

I'd love to see CKSource commit to maintaining CKEditor 4 as long as there are accessibility errors in 5 that weren't in 4. Authors are depending on using CKEditor and we don't want to suddenly give authors no ability to create content through our WYSIWYG. Any reversion in accessibility is serious!

I am also hopeful that this will be fixed in CKEditor 5 before it goes into production. We absolutely want to have users with disabilities testing the beta, but my main concern is that sites start upgrading to Drupal 10 and we start blocking folks off from editing their content.

I would also want to ensure that if CKEditor 5 isn't fixed in time that we include this work around to reverting to CKEditor 4 in our release notes until it is fixed.

I was not able to replicate this bug on my Mac's Voice Control tool & Edge.

FYI that there's some recent discussion about this bug in https://github.com/ckeditor/ckeditor5/issues/2045#issuecomment-1295134733 and later comments. I don't know what the conclusion is yet from those comments, but just linking to it in case anyone following this issue wants to follow that one.

In the issue mentioned in #16 there was evidence that iOS dictation did not work in CKEditor4, suggesting that CKEditor 5 may not be experiencing a regression. However, after meeting with CK source, we established that this was due to testing with the iOS keyboard substitute dictation feature, as opposed to the voice control feature, which is how I had been testing this feature. With voice control, there is no problem in CKEditor 4. With the current CKEditor5 release, this is still a problem. I have also confirmed that once the changes here have landed, this will be fixed.

@catch, @bnjmnm, @Gábor Hojtsy, and I discussed this. Given #18, we're not going to block Drupal 10's RC1 on this, and will instead target it for RC2, or whichever RC number we're on when that CKE5 patch release is ready.

I get the same changes locally, patch looks good to me, this is good to go if the tests pass.

Committed and pushed 279faa2e26 to 10.1.x and 4c16b09caa to 10.0.x. Thanks!
Committed ce4429b and pushed to 9.5.x. Thanks!
Committed 810f211 and pushed to 9.4.x. Thanks!