feat: make recipe cards interactive with detail page and Run Match

[touchthesun]

Summary

• Recipe cards on the cooking-domain browse page were static text — no way to open a recipe or run a match from the list, unlike design cards.
• Add RecipeDetailView (mirroring OkhDetailView's breadcrumb/title/actions layout) rendered at the existing okh/:id route when domain=cooking, reusing the already-cached ["recipes"] query since there's no per-recipe fetch endpoint.
• Link each recipe card's body to its detail page, and add a "Run Match ⚡" action on both the card and the detail page that navigates to /match?recipe_id=<id>.
• MatchPage/CookingMatchView now read recipe_id from the URL and preselect it in RecipePicker, mirroring how okh_id preselects a design on the hardware match page.

Test plan

• npm run typecheck
• npm run lint (no new warnings/errors on touched files)
• npm run test:unit — 346/346 passing, including new tests for RecipeListView, RecipeDetailView, and CookingMatchView's initialRecipeId preselect
• Manually click through a recipe card → detail page → Run Match on a deployed cooking-domain instance

Made with Cursor