fix(ecs): type IEngine.removeEntity as boolean, matching what it returns

Review follow-up. The tests assert that removeEntity returns false for a
refused reserved-entity removal, but IEngine declared it `void`, so no caller
could act on that without a cast — `if (!engine.removeEntity(e))` does not
compile against a void return.

The mismatch predates this branch: main already ended removeEntity with
`return entityContainer.removeEntity(entity)`, and IEntityContainer has
always typed that as boolean. The API report shows both side by side, one
`void` and one `boolean`. What changed here is that the value became
meaningful — false now specifically means "refused, components untouched" —
so this is the right place to stop the type lying about it.

Non-breaking: widening a return type does not affect callers that ignore it,
and nothing implements IEngine. The only `Pick<IEngine, ... 'removeEntity'>`
consumers are removeEntityWithChildren / removeNetworkEntityChildrens in
tree.ts, both fed the internal removeEntity, which already returns boolean.

removeEntityWithChildren is deliberately left `void`: it delegates to
removeNetworkEntityChildrens, which is genuinely void, and iterates a tree
where a per-entity result has no single meaning.

Public API surface changes by exactly one line, regenerated via `make build`:
  -    removeEntity(entity: Entity): void;
  +    removeEntity(entity: Entity): boolean;

Bundle snapshots are unchanged, as expected for a types-only edit. Full suite
green: 160 suites, 1216 tests.

Author: LautaroPetaccio

packages/@dcl/ecs/src/engine/types.ts

@@ -92,8 +92,18 @@ export interface IEngine {
    * @public
    * Remove all components of an entity
    * @param entity - entity
+   * @returns true if the entity was removed; false if the removal was refused, leaving the
+   *   entity's components untouched. A removal is refused when the entity's NUMBER falls in
+   *   the renderer-reserved range (`RESERVED_STATIC_ENTITIES`): the root, player and camera
+   *   entities, plus the range the avatar system allocates remote players from. Those belong
+   *   to the renderer rather than the scene, and purging them locally desynchronizes the
+   *   scene with no way back — the outgoing deletes are dropped by the renderer's scene
+   *   write guard, so it keeps the entity alive and never re-sends the components.
+   *
+   *   The check is on the entity NUMBER, so it holds at every version: `#32 v1` packs to
+   *   `65568` and is refused just as `#32 v0` is.
    */
-  removeEntity(entity: Entity): void
+  removeEntity(entity: Entity): boolean
 
   /**
    * Remove all components of each entity in the tree made with Transform parenting

packages/@dcl/playground-assets/etc/playground-assets.api.md

@@ -1461,7 +1461,7 @@ export interface IEngine {
     registerComponentDefinition<T>(componentName: string, componentDefinition: ComponentDefinition<T>): ComponentDefinition<T>;
     // (undocumented)
     removeComponentDefinition(componentId: number | string): void;
-    removeEntity(entity: Entity): void;
+    removeEntity(entity: Entity): boolean;
     removeEntityWithChildren(entity: Entity): void;
     removeSystem(selector: string | SystemFn): boolean;
     readonly RootEntity: Entity;