Resolve @template bindings in Arrayable shapes and Builder method return types

[levikl]

summary

this change parses and stores @template, @template-covariant, and @template-contravariant docblock tags on ClassLikeResult, giving every analyzed class a typed record of its generic parameters.

e2e flow

given a controller returning Product::paginate(5) inside an Inertia::render() call:

1. Product::paginate(5) falls back to Builder::paginate() since Product doesn't define it
2. Builder's ClassLikeResult::templateTags() contains TModel of Model
3. bindCallerTemplates -> ["TModel" => ClassType(Product)]
4. substituteInType replaces StringType("TModel") -> ClassType(Product)
5. result: ClassType(LengthAwarePaginator, genericTypes: [IntType, ClassType(Product)])
6. ArrayableResolver resolves LengthAwarePaginator::toArray(); data key contains StringType('TKey')|StringType('TValue') placeholders because the Collection::toArray() fast path surfaces them directly from the collection's generic types
7. substituteTemplateBindings maps TKey -> IntType, TValue -> ClassType(Product)
8. data: App.Models.Product[] emitted in generated TypeScript

related

• add generic return types to Builder paginate methods framework#60045
• next: paginated Eloquent response type narrowing wayfinder#249

merge order

laravel/framework#60045 -> this -> laravel/wayfinder#249

[joetannenbaum]

Thanks for the PR! Is this ready to be looked at? Or is it still a draft?

[levikl]

@joetannenbaum yo! saw the direction you're taking with generics in #40 so I went ahead and refactored this to fit naturally alongside it, eg. storing @template declarations from class docblocks in ClassLikeResult and using them to substitute concrete types through Arrayable and Builder return type resolution.

this is ready for review