feat!: move result type to the first type parameter

[devCrossNet]

What is accomplished by your PR?

The result type is now the first type parameter. TypeScript does not allow skipping leading type parameters, so before this change all defaults had to be repeated to set the result type.

// before
new Quaire<QuaireItem, QuaireQuestion, QuaireNavigationItem, MyResult>({ items });

// after
new Quaire<MyResult>({ items });

New order:

Type	Order
Quaire	<Result, Item, Question, NavigationItem>
QuaireBase	<Result, Question, NavigationItem>
QuaireOptions	<Result, Item, NavigationItem>

• README and the extending-data-definition example are updated
• New type test: the result type is inferred from the result option without explicit type arguments

Is there something controversial in your PR?

Breaking change for subclasses with custom types (planned for 1.0):

class MyQuaire extends Quaire<QuaireResult, MyItem, MyQuestion, MyNavigationItem> {}

Checklist

• Run unit tests to ensure all existing tests are still passing
• Add new passing unit tests to cover the code introduced by your PR
• Change documentation for the code introduced by your PR

🤖 Generated with Claude Code