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/framework/behavior-tree/src/index.ts

@@ -0,0 +1,67 @@
+/**
+ * @esengine/behavior-tree
+ *
+ * @zh AI 行为树系统，支持运行时执行和可视化编辑
+ * @en AI Behavior Tree System with runtime execution and visual editor support
+ *
+ * @zh 此包是通用的行为树实现，可以与任何 ECS 框架配合使用。
+ * 对于 ESEngine 集成，请从 '@esengine/behavior-tree/esengine' 导入插件。
+ *
+ * @en This package is a generic behavior tree implementation that works with any ECS framework.
+ * For ESEngine integration, import the plugin from '@esengine/behavior-tree/esengine'.
+ *
+ * @example Cocos/Laya/通用 ECS 使用方式:
+ * ```typescript
+ * import {
+ *     BehaviorTreeAssetManager,
+ *     BehaviorTreeExecutionSystem,
+ *     BehaviorTreeRuntimeComponent
+ * } from '@esengine/behavior-tree';
+ *
+ * // 1. Register service
+ * Core.services.registerSingleton(BehaviorTreeAssetManager);
+ *
+ * // 2. Load behavior tree from JSON
+ * const assetManager = Core.services.resolve(BehaviorTreeAssetManager);
+ * assetManager.loadFromEditorJSON(jsonContent);
+ *
+ * // 3. Add component to entity
+ * entity.addComponent(new BehaviorTreeRuntimeComponent());
+ *
+ * // 4. Add system to scene
+ * scene.addSystem(new BehaviorTreeExecutionSystem());
+ * ```
+ *
+ * @packageDocumentation
+ */
+
+// Constants
+export { BehaviorTreeAssetType } from './constants';
+
+// Types
+export * from './Types/TaskStatus';
+export type { IBTAssetManager, IBehaviorTreeAssetContent } from './Types/AssetManagerInterface';
+
+// Execution (runtime core)
+export * from './execution';
+
+// Utilities
+export * from './BehaviorTreeStarter';
+export * from './BehaviorTreeBuilder';
+
+// Serialization
+export * from './Serialization/NodeTemplates';
+export * from './Serialization/BehaviorTreeAsset';
+export * from './Serialization/EditorFormatConverter';
+export * from './Serialization/BehaviorTreeAssetSerializer';
+export * from './Serialization/EditorToBehaviorTreeDataConverter';
+
+// Services
+export * from './Services/GlobalBlackboardService';
+
+// Blackboard types (excluding BlackboardValueType which is already exported from TaskStatus)
+export type { BlackboardTypeDefinition } from './Blackboard/BlackboardTypes';
+export { BlackboardTypes } from './Blackboard/BlackboardTypes';
+
+// Service tokens (using ecs-framework's createServiceToken, not engine-core)
+export { BehaviorTreeSystemToken } from './tokens';