feat: editorInfo migrate to globalService

[chilingling]

English | 简体中文

PR

PR Checklist

Please check if your PR fulfills the following requirements:

• [x] The commit message follows our Commit Message Guidelines
• [ ] Tests for the changes have been added (for bug fixes / features)
• [ ] Docs have been added / updated (for bug fixes / features)
• [ ] Built its own designer, fully self-validated

PR Type

What kind of change does this PR introduce?

• [ ] Bugfix
• [x] Feature
• [ ] Code style update (formatting, local variables)
• [ ] Refactoring (no functional changes, no api changes)
• [ ] Build related changes
• [ ] CI related changes
• [ ] Documentation content changes
• [ ] Other... Please describe:

Background and solution

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• [x] Yes
• [ ] No

Other information

Summary by CodeRabbit

• New Features

  • Introduced a lifecycle hook for asynchronous initialization before application creation.
  • Added a new function for initializing application data and managing user information.
  • Implemented a service definition function for reactive state management.

• Improvements

  • Shifted to centralized state management by replacing direct editor info dependencies with a global service approach across multiple components.
  • Enhanced application extensibility and maintainability through structured lifecycle management and data handling.

• Bug Fixes

  • Removed unused services, streamlining module dependencies and improving overall maintainability.