feat(schema): scan app loaders from @decocms/apps

[guitavano]

Summary

• Add a static mapping of 8 CMS keys → 3 unique inline-loader source files from @decocms/apps (productListShelf, productListingPage, productDetailsPage)
• Parse each source file once via ts-morph and register them in definitions, loaderBlocks, loaderRootAnyOf, and outputTypeToLoaderKeys
• Section block-ref props (ProductShelf.products, SearchResult.page) and commerce extension wrappers now automatically include app loaders in their anyOf

Test plan

• Ran generate-schema.ts --site casaevideo — all 8 app loaders scanned with correct output types
• ProductShelf.products anyOf includes vtex/loaders/intelligentSearch/productList.ts + aliases
• SearchResult.page anyOf includes vtex/loaders/intelligentSearch/productListingPage.ts + aliases
• Commerce extension wrapper listingPage data field includes 3 PLP loaders
• CI passes

🤖 Generated with Claude Code

---

Summary by cubic

Scan and register inline app loaders from @decocms/apps, and fix array output type detection so block-ref fields surface the correct loader pickers.

• New Features

  • Map 8 CMS keys to 3 inline loaders from @decocms/apps and add them to definitions, loaderBlocks, and root anyOf.
  • Block-refs like ProductShelf.products and SearchResult.page now include the app loaders; the commerce listingPage wrapper lists the 3 PLP loaders.

• Bug Fixes

  • Resolve array return types as Product[] (not Array) to avoid collisions in loader→section matching.
  • For array or nullable-array props, match on the element type to find the right loaders.

^{Written for commit 5c64018. Summary will update on new commits.}