fix: make LexicalRichText more accessible

[mkilpatrick]

This change completely removes Lexical's ContentEditable component and instead renders the html directly, rather than making an editable area readonly. It addresses an accessibility audit:

• role="textbox" → announces as editable to screen readers.
• contenteditable="false" → contradicts the role; it’s not actually editable.
• Not keyboard-focusable (no tabindex, not natively interactive).
• Impact: Screen readers think it’s an editable text field, but:
  - It cannot be focused with Tab.
  - It isn’t actually editable.
  - It isn’t a native control ( or <textarea>).

Note that this still renders client side only.

[changeset-bot]

⚠️ No Changeset found

Latest commit: e39c328

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR