feat(create): guided wizard with use-case and language filters

[l2ysho]

Closes #1236.

Reshapes apify create into the guided wizard from the epic: use case → language → best-match template, plus a new apify templates ls command. Local scaffold only (--source apify); the Git path stays a separate sub-issue.

What changed

• New wizard flow in apify create: prompts for "What do you want to build?" (use case) and the language, then shows one scrollable, fit-ranked template list — exact matches first with the top one preselected, a non-selectable separator (── The templates below don't exactly match your selection ──), then the closest alternatives in tier order.
• New flags -u/--use-case and -l/--language. -t/--template stays authoritative and bypasses the wizard entirely; -u/-l are ignored when -t is given (stated in the flag descriptions).
• New command apify templates ls [--json] — human table by default; --json emits the full template objects including useCases[], so agents can discover the enum values without scraping --help.
• Ported algorithm getTemplateRecommendation from apify-core, with the two CLI-specific changes agreed on the issue: a per-template isExactMatch flag (no aggregate boolean) and no result limit (tier order already sorts most→least fitting).

Flag → manifest-id mapping

--use-case	manifest id		--language	manifest category
web-scraping	WEB_SCRAPING		javascript	javascript
ai-agent	AI		typescript	typescript
api-pipeline	INTEGRATION		python	python
browser-automation	AUTOMATION		other	(BYO Docker — see below)

"Skip (show all)" in the use-case prompt and "Any language" in the language prompt both mean no filter (the algorithm's exact match then reduces to the remaining dimension, or everything when both are skipped).

Notes for reviewers

• -l other (BYO Docker) is kept as a valid flag value even though no manifest template matches it today (per the team decision on Guided apify create wizard: use-case → language → best-match template #1236). It's a flag-only escape hatch — not offered in the interactive prompt — and currently falls through to showing all templates with no exact match. Full BYO-Docker scaffolding is out of scope here.
• Console handoff: since Console works in raw ids (e.g. ?useCase=WEB_SCRAPING), the Console "Use locally" emit will need its own id→kebab mapping when it builds the apify create line.
• Stale research callout: the research note claimed "Browser automation + JavaScript" was the only zero-exact-match combo. The manifest has since added js-cypress (JavaScript + AUTOMATION), so that pair now has an exact match. The zero-exact "no exact match — showing the closest alternatives" hint path is still covered by a synthetic-fixture unit test.
• The old install-confirmation prompt and per-template "Go back" affordance were dropped as part of the wizard redesign; dependency install remains governed by --skip-dependency-install.

Test plan

• New unit tests: getTemplateRecommendation (tiers, dedup, any-language, skip-use-case, BYO-other, no-exact) and buildTemplateChoiceList (separator placement, language-suffix labels, hint text). 31 relevant tests green (incl. existing create tests).
• pnpm run build, pnpm run lint, pnpm run format — clean. docs/reference.md regenerated via pnpm run update-docs.
• Drove the wizard end-to-end in a real terminal: use-case → language → template prompts render correctly, top item preselected, and the selected template scaffolds.

🤖 Generated with Claude Code