fix(bindx): resolve auto-generated has-many alias on accessor reads (#53)

[matej21]

Closes #53.

Problem

A has-many relation selected with params (orderBy/filter/limit/offset) reads back as an empty list on the resulting accessor — list.items[i].<relation>.items is always []. Scalar siblings load fine; dropping the params makes the relation populate. The data is fetched correctly; it's lost between store and accessor.

Root cause

A has-many with params gets an auto-generated alias (generateHasManyAlias → tags_<hash>), so the fetched rows land in the entity snapshot under data['tags_<hash>']. The read path had two gaps:

1. useEntity / useEntityList never threaded the selection into the root EntityHandle, so this.selection was undefined and no alias could be resolved.
2. EntityHandle.fields passed undefined as the alias to hasMany(), so HasManyListHandle looked under data['tags'] (empty) instead of data['tags_<hash>'].

The consumer reads the relation by its real field name (tags) — it can't know the hash alias — so the read side must map field name → stored alias.

Fix

• EntityHandle — new resolveSelectionField(name): direct lookup first, then for array relations falls back to matching on fieldName, recovering the auto-generated alias. The resolved alias + nested selection are threaded into hasMany(). The fallback is restricted to has-many so explicit scalar/has-one aliases still report unfetched when read by their original name.
• useEntity / useEntityList — pass selectionMeta to the root EntityHandle (+ dep arrays).

This also makes the hooks selection-aware (UnfetchedFieldError), consistent with the already-validating <Entity> JSX path — it completes the existing selection design rather than changing it.

Tests

• tests/react/hooks/useEntityList/nestedHasManyOrderBy.test.tsx — the reported repro (list path).
• tests/react/hooks/useEntity/nestedHasManyOrderBy.test.tsx — companion single-entity path, also asserting orderBy is honored on read.

Verification

• Full suite: only pre-existing failures remain — 9 tests/browser/* (need the live playground) and FormHasManyRelationScope › tracks dirty state (fails identically on clean main, verified in a worktree). Zero new failures.
• Typecheck clean for the changed packages (the lone packages/example/App.tsx error is a pre-existing duplicate @contember/graphql-client install).

🤖 Generated with Claude Code