V16: Migrate TinyMCE data type configuration to Tiptap

[Zeegaan]

Description

Migrates the data type configuration of TinyMCE rich-text editors over to Tiptap.

How to test?

• on v16/dev, create a TinyMCE rich-text editor datatype, (more with different configurations would be ideal)
• Switch to this branch
• Run the site, it should redirect you to /umbraco/upgrade, run the migration
• Assert that your rich-text editor has been migrated to Tiptap, and has the same configuration (mainly toolbar)
• We should also test that we can disable this migration, if we do not want to migrate (for example, if you have the TinyMCE package installed)
• Do the same as above, but instead before running the migration, create a new class in your Web.UI project, and paste in the following code:

using Umbraco.Cms.Core.Composing;
using Umbraco.Cms.Core.Configuration.Models;

namespace Umbraco.Cms.Web.UI;

public class MyConfigureOptions : IComposer
{
    public void Compose(IUmbracoBuilder builder)
    {
        builder.Services.Configure<TinyMceToTiptapMigrationSettings>(settings =>
        {
            settings.DisableMigration = true;
        });
    }
}

• Assert that your RTE did NOT get migrated over to Tiptap 😁

[Copilot]

Pull Request Overview

This PR migrates the TinyMCE rich text editor configuration to TipTap and introduces an option to disable the migration. Key changes include:

• Adding MigrateRichtextEditorToTiptap to transform toolbar settings and update the editor alias.
• Updating the upgrade plan to include the new migration step.
• Registering and defining the TipTapMigrationSettings model for conditional migration.

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
MigrateRichtextEditorToTiptap.cs	Implements migration logic from TinyMCE to TipTap with toolbar item mapping
UmbracoPlan.cs	Schedules the new migration in the upgrade plan with a unique GUID
UmbracoBuilder.Configuration.cs	Registers TipTapMigrationSettings via dependency injection
TipTapMigrationSettings.cs	Adds a configuration model to optionally disable the migration

Comments suppressed due to low confidence (2)

src/Umbraco.Infrastructure/Migrations/Upgrade/V_16_0_0/MigrateRichtextEditorToTiptap.cs:42

• [nitpick] Consider renaming 'toolBarList' to 'toolbarList' for consistency with common naming conventions in the codebase.

if (!dataType.ConfigurationData.TryGetValue("toolbar", out var toolbar) || toolbar is not List<string> toolBarList)

src/Umbraco.Infrastructure/Migrations/Upgrade/V_16_0_0/MigrateRichtextEditorToTiptap.cs:51

• Consider adding unit tests for the MapToolbarItem method to ensure all toolbar items are correctly mapped during the migration.

private string? MapToolbarItem(string item)

[leekelleher]

@Zeegaan Tested out with the various scenarios, all looking good! 🚀 🙌

To note, I have renamed the migration and settings class to include a reference to TinyMCE. From a 3rd-party perspective, it helps to clarify the intention of the migration/disabling config.
I hope this is okay, apologies for not discussing with you beforehand.

I also set the default result of the switch to return null, as if a TinyMCE toolbar alias doesn't map to one of our known Tiptap toolbar extensions, then it may cause an issue with rendering the toolbar.