refactor!: use type aliases and replace any with exact types

[devCrossNet]

What is accomplished by your PR?

Interfaces → type aliases

• All interfaces in src and examples are now type aliases
• src/interfaces.ts is renamed to src/types.ts
• Generic parameters IItem, IQuestion, INavigationItem are renamed to Item, Question, NavigationItem

any → exact types (27 of 32 replaced)

• Inputs (saveAnswer, answer parameters, QuaireOptions.result, QuaireItem.defaultValue) use unknown
• getByPath is generic, isNil is a type guard
• as any casts are replaced: objects are built as QuaireQuestion / QuaireNavigationItem and then cast to the generic type
• 5 outputs stay any on purpose (getResult(), _result, QuaireQuestion.value, QuaireQuestion.defaultValue, QuaireNavigationItem.value), because consumers read them directly

Types fixed to match runtime values

Type	Before	After
QuaireNavigationItem.value	string	any (arrays, booleans, null)
QuaireNavigationItem.componentType	no null	| null (parents without question)
QuaireQuestion.navigationItemId	required	optional
QuaireQuestion.selectOptions / rangeOption / inputOption	no null	| null

ESLint rules

• @typescript-eslint/consistent-type-definitions: type
• @typescript-eslint/naming-convention: no I prefix for types
• @typescript-eslint/no-explicit-any enabled, the 5 exceptions are documented inline

Is there something controversial in your PR?

Breaking changes for TypeScript consumers:

• Declaration merging of Quaire types is no longer possible
• null must be handled for the fixed types listed above with strict mode
• Direct imports from quaire/dist/interfaces break (now dist/types)

Normal imports from quaire and interface X extends QuaireItem in consumer code still work.

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