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/blueprint/src/index.ts

@@ -0,0 +1,67 @@
+/**
+ * @esengine/blueprint - Visual scripting system for ECS Framework
+ *
+ * @zh 蓝图可视化脚本系统 - 可与任何 ECS 框架配合使用
+ * @en Visual scripting system - works with any ECS framework
+ *
+ * @zh 此包是通用的可视化脚本实现，可以与任何 ECS 框架配合使用。
+ * 对于 ESEngine 集成，请从 '@esengine/blueprint/esengine' 导入插件。
+ *
+ * @en This package is a generic visual scripting implementation that works with any ECS framework.
+ * For ESEngine integration, import the plugin from '@esengine/blueprint/esengine'.
+ *
+ * @example Cocos/Laya/通用 ECS 使用方式:
+ * ```typescript
+ * import {
+ *     createBlueprintSystem,
+ *     createBlueprintComponentData
+ * } from '@esengine/blueprint';
+ *
+ * // Create blueprint system for your scene
+ * const blueprintSystem = createBlueprintSystem(scene);
+ *
+ * // Create component data
+ * const componentData = createBlueprintComponentData();
+ * componentData.blueprintAsset = loadedAsset;
+ *
+ * // Add to your game loop
+ * function update(dt) {
+ *     blueprintSystem.process(blueprintEntities, dt);
+ * }
+ * ```
+ *
+ * @packageDocumentation
+ */
+
+// Types
+export * from './types';
+
+// Runtime
+export * from './runtime';
+
+// Triggers
+export * from './triggers';
+
+// Composition
+export * from './composition';
+
+// Nodes (import to register)
+import './nodes';
+
+// Re-export commonly used items
+export { NodeRegistry, RegisterNode } from './runtime/NodeRegistry';
+export { BlueprintVM } from './runtime/BlueprintVM';
+export {
+    createBlueprintComponentData,
+    initializeBlueprintVM,
+    startBlueprint,
+    stopBlueprint,
+    tickBlueprint,
+    cleanupBlueprint
+} from './runtime/BlueprintComponent';
+export {
+    createBlueprintSystem,
+    triggerBlueprintEvent,
+    triggerCustomBlueprintEvent
+} from './runtime/BlueprintSystem';
+export { createEmptyBlueprint, validateBlueprintAsset } from './types/blueprint';