Create documentation for supported editors on developer.yoast.com

Start by checking the blocked issue #226, then inspect developer/docs/features/analysis and existing Docusaurus pages. Create the editors/overview.md and editor-specific pages for Classic, Block, and Elementor, documenting supported assessments and relevant content types. Done means the pages use the requested front matter, link to assessment documentation, and cover the listed editor-specific notes.

Please give us a description of the issue

• I've read and understood the contribution guidelines.
• I've searched for any related issues and avoided creating a duplicate issue.

This task was created as part of this task: https://github.com/Yoast/non-dev-tasks/issues/39
See report in first comment to this task for context.

Blocked by https://github.com/Yoast/developer/issues/226

Supported editors

In developer/docs/features/analysis create a folder called editors.

overview.md

Within this folder we create one overview.md with some general information and links to all editor specific docs.

This should have a docusaurus header like so:

---
id: overview
title: "Editors: Overview"
sidebar_label: Overview
description: This documentation provides documentationon all our supported editors.
---

List of supported editors

• Classic
• Block
• Elementor

Editors specific pages.

Should have headers like such

---
id: classicEditor
title: "Editors: Classic editor"
sidebar_label: Classic Editor
description: This documentation provides information on the classic editor and what assessments are suopported and how.
---

This could contain a table of all Assessments (with hyperlink to their docusaurus page) and some additional information

For classic editor,

• Make notes about taxonomies also using Classic?
• Make notes about Woo products also using classic?
• Make notes about Shopify, which also uses tinyMCE?

For block editor,

• Make notes about Gutenberg being (in principle) the same as Block editor.

For Elementor,

• Make note about products in elementor.

Assessment	Content type Specific config
Keyphrase in introduction	❌
Keyphrase length	❌
...	...

Think about what other columns might be relevant to add to this overview.