V15: Adds migration of data type configuration when changing property editor UI

[iOvergaard]

Description

This pull request includes changes to the UmbDataTypeWorkspaceContext class and updates to the acceptance tests for data types. The main focus is on improving the handling of default data and ensuring that configurations are transferred correctly.

It adds a comparer that keeps useful data around when migrating from one property editor ui to another. Currently, it compares based on the alias, so if it's the same, it will keep the data. This is similar behavior to V13. I added a TODO to potentially find the schema alias and compare based on that, but we currently do not have that available at that point in the code.

This is useful when migrating from tinymce to tiptap, for example, but also Number -> Decimal, Text Area -> Text Box, and other similar data types.

Changes to data type handling:

• src/Umbraco.Web.UI.Client/src/packages/data-type/workspace/data-type-workspace.context.ts: Updated the UmbDataTypeWorkspaceContext class to properly transfer default data from the schema and UI while preserving existing data that is not in the default data.

Updates to acceptance tests:

• tests/Umbraco.Tests.AcceptanceTest/tests/DefaultConfig/DataType/DataType.spec.ts: Added a maxChars parameter to the createTextstringDataType method and included a test to verify that the maxChars setting is correctly transferred and stored. [1] [2]

How to test

1. Set up a data type with TinyMCE as the editor ui
2. Click "Change" and switch to Tiptap
3. Check that all comparable configuration data is transferred/migrated, for example that blocks are still configured

[leekelleher]

Tested it out TinyMCE to Tiptap, and also between other compatible property-editors, e.g. Checkbox List to Radiobutton List (and others with the "items" configuration field); the numeric editors (Decimal and Integer). All working well. 🚀