feat: new plugin configuration method

[nshenderov]

What does it do?

Introduces a new setPluginConfig method to configure the plugin in the front-end environment. This method must be invoked before the admin panel's bootstrap lifecycle function.

function setPluginConfig(pluginConfig: PluginConfig): void

Example:

// src/admin/app.tsx
import { type PluginConfig, setPluginConfig } from '@_sh/strapi-plugin-ckeditor';

const pluginConfig: PluginConfig = {
  presets: [
  {
    //The `field` property has been replaced by `name` and `description` properties.
    name: 'default',
    description: 'Default editor',
    editorConfig: {...}
  },
  ...
  ],
  // theme: {...},
}

export default {
  register() {
    setPluginConfig(pluginConfig);
  },
};

Why is it needed?

Configuring CKEditor (a front-end plugin) directly in the front-end environment makes it easier to handle non serializable data types. This approach eliminates crutches such as: the need to write configurations in the Node.js environment, convert them to text, and expose them as global variables. With this update, all editor plugins can be imported directly alongside their configuration objects as expected, without the need to expose them to the global object.

Breaking Changes

• ckeditor.js|ts file is no longer supported for plugin configuration. The plugin now requires using the setPluginConfig method for configuration. Existing setups must be updated to call this method before the admin panel's bootstrap lifecycle.
• The plugin doesn't expose any ckeditor packages to the global object anymore.
• The field property has been replaced by name and description properties.
• dontMergePresets and dontMergeTheme options have been removed. User-provided configuration objects now completely overwrite the default ones.