Dependency to the old ckeditor breaks upgrade from D9 to D10

Thanks! After thinking about this, I don't think there should be a dependency on CKEditor at all, either ckeditor or ckeditor5. This module provides a plugins for CKEditor 4 and CKEditor 5, but it also provides a field widget for the core Link field. So, in theory, someone could want to use this module only in that context, without CKEditor. This scenario may be more common in the future when ✨ Drastically improve the linking experience in CKEditor 5 Needs work lands in core.

Actually, now that I look at the linkit.info.yml file rather than the diff, I see that the dependency on drupal:ckeditor is in test_dependencies. This makes more sense, since our team uses this module heavily with codebases that do not have ckeditor (4) present.

It is therefore my hypothesis that the error In ExtensionList.php line 522: The module ckeditor does not exist.. may not in fact be coming from Linkit's declaration of drupal:ckeditor in test_dependencies.

Therefore, I'd like to have further confirmation -- a demonstration of steps to reproduce with a generic Drupal 9 to 10 update -- before proceeding with removing a test dependency. Specifically, provide steps to reproduce that shows that a removal of ckeditor from core.extension in the site configuration and a programmatic uninstall of ckeditor prior to the drush cim still results in the error, and that the removal of the test_dependency resolves it, rather than a repeated drush cim.

Thanks, bojan!

After some retesting, I figured out it had todo with core.extensions in my DB, had to write a hook_update to disable ckeditor before running drush cim. My bad, I will close the issue.