refactor: reorganize package structure and decouple framework packages (#338)

* refactor: reorganize package structure and decouple framework packages

## Package Structure Reorganization
- Reorganized 55 packages into categorized subdirectories:
  - packages/framework/ - Generic framework (Laya/Cocos compatible)
  - packages/engine/ - ESEngine core modules
  - packages/rendering/ - Rendering modules (WASM dependent)
  - packages/physics/ - Physics modules
  - packages/streaming/ - World streaming
  - packages/network-ext/ - Network extensions
  - packages/editor/ - Editor framework and plugins
  - packages/rust/ - Rust WASM engine
  - packages/tools/ - Build tools and SDK

## Framework Package Decoupling
- Decoupled behavior-tree and blueprint packages from ESEngine dependencies
- Created abstracted interfaces (IBTAssetManager, IBehaviorTreeAssetContent)
- ESEngine-specific code moved to esengine/ subpath exports
- Framework packages now usable with Cocos/Laya without ESEngine

## CI Configuration
- Updated CI to only type-check and lint framework packages
- Added type-check:framework and lint:framework scripts

## Breaking Changes
- Package import paths changed due to directory reorganization
- ESEngine integrations now use subpath imports (e.g., '@esengine/behavior-tree/esengine')

* fix: update es-engine file path after directory reorganization

* docs: update README to focus on framework over engine

* ci: only build framework packages, remove Rust/WASM dependencies

* fix: remove esengine subpath from behavior-tree and blueprint builds

ESEngine integration code will only be available in full engine builds.
Framework packages are now purely engine-agnostic.

* fix: move network-protocols to framework, build both in CI

* fix: update workflow paths from packages/core to packages/framework/core

* fix: exclude esengine folder from type-check in behavior-tree and blueprint

* fix: update network tsconfig references to new paths

* fix: add test:ci:framework to only test framework packages in CI

* fix: only build core and math npm packages in CI

* fix: exclude test files from CodeQL and fix string escaping security issue

packages/rendering/sprite/src/SpriteRuntimeModule.ts

@@ -0,0 +1,56 @@
+import type { IComponentRegistry, IScene } from '@esengine/ecs-framework';
+import type { IRuntimeModule, IRuntimePlugin, ModuleManifest, SystemContext } from '@esengine/engine-core';
+import { SpriteComponent } from './SpriteComponent';
+import { SpriteAnimatorComponent } from './SpriteAnimatorComponent';
+import { SpriteAnimatorSystem } from './systems/SpriteAnimatorSystem';
+import { SpriteAnimatorSystemToken } from './tokens';
+
+export type { SystemContext, ModuleManifest, IRuntimeModule, IRuntimePlugin };
+
+// 重新导出 tokens | Re-export tokens
+export { SpriteAnimatorSystemToken } from './tokens';
+
+class SpriteRuntimeModule implements IRuntimeModule {
+    registerComponents(registry: IComponentRegistry): void {
+        registry.register(SpriteComponent);
+        registry.register(SpriteAnimatorComponent);
+    }
+
+    createSystems(scene: IScene, context: SystemContext): void {
+        const animatorSystem = new SpriteAnimatorSystem();
+
+        if (context.isEditor) {
+            animatorSystem.enabled = false;
+        }
+
+        scene.addSystem(animatorSystem);
+
+        // 注册服务到服务注册表 | Register service to service registry
+        context.services.register(SpriteAnimatorSystemToken, animatorSystem);
+    }
+}
+
+const manifest: ModuleManifest = {
+    id: 'sprite',
+    name: '@esengine/sprite',
+    displayName: 'Sprite 2D',
+    version: '1.0.0',
+    description: 'Sprite and SpriteAnimator components for 2D rendering',
+    category: 'Rendering',
+    icon: 'Image',
+    isCore: false,
+    defaultEnabled: true,
+    isEngineModule: true,
+    canContainContent: true,
+    dependencies: ['core', 'math'],
+    exports: { components: ['SpriteComponent', 'SpriteAnimatorComponent'] },
+    editorPackage: '@esengine/sprite-editor',
+    requiresWasm: true
+};
+
+export const SpritePlugin: IRuntimePlugin = {
+    manifest,
+    runtimeModule: new SpriteRuntimeModule()
+};
+
+export { SpriteRuntimeModule };