Fix wildcard queries for dontFragment relations

[Copilot]

Wildcard relation queries like relation(ChildOf, '*') failed to match entities when the component had dontFragment: true. This occurred because dontFragment relations are stored separately from archetype signatures to prevent fragmentation, but wildcard matching only checked archetype component types.

Changes

• Archetype matching: Added hasRelationWithComponentId() to check both archetype components and per-entity dontFragment relations
• Query filtering: Modified Query.getEntities() to filter at entity level for wildcard queries, since dontFragment archetypes can contain entities with/without the relation
• Iteration support: Updated buildWildcardRelationValue() to include dontFragment relations when iterating with forEach()

Example

const ChildOf = component({ dontFragment: true });
const parent1 = world.new();
const parent2 = world.new();

const child1 = world.new();
world.set(child1, relation(ChildOf, parent1));

const child2 = world.new();
world.set(child2, relation(ChildOf, parent2));

world.sync();

// Previously returned 0 entities, now correctly returns both
const query = world.createQuery([relation(ChildOf, "*")]);
const entities = query.getEntities(); // [child1, child2]

Original prompt

发现对于dontFragment的组件，wildcard查询失效了，如查询relation(ChildOf, '*')，在ChildOf为dontFragment组件时无法查询到，请编写测试并修复这个问题

The user has attached the following file paths as relevant context:

• src/world.ts
• src/archetype.ts
• src/entity.ts
• .github/copilot-instructions.md

Created from VS Code via the GitHub Pull Request extension.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[codehz]

@copilot getMatchingArchetypes 的改动存在问题：由于dont fragment component 的变化不会影响archetype的shape，因而当entity添加这种组件时不会在后续触发 checkNewArchetype，这导致这个写法可能错误的提前过滤了archetype，query可能会漏了这部分实体
一个想法是，设立一个wildcard relation的index，标记到archetype的签名里，这里可以参考 flecs 的设计 （我们只需要处理(Comp, *)这种情况）