fix: #3627367 List the Podcasts page from the podcasts view instead of static cards

The Podcasts page placed six podcast-card components with literal titles, episode counts and images. Only one of the six linked anywhere; the other five pointed at /podcasts itself, and none of the six shows existed as content.

Replacing them with the real view also fixes the spacing this issue was opened about, so the earlier two-row change is dropped.

What changed

• recipe.yml repoints views.view.podcasts at the site-template theme, alongside the views.view.news and views.view.blog actions already there. varbase_podcasts_base ships the view with vartheme_bs5: component ids, and that theme is not installed on a RightUp site, so every one of its block displays raised Twig\Error\LoaderError: Template "vartheme_bs5:grid" is not defined. The view has never rendered on RightUp.
• content/canvas_page/08-podcasts.yml places block.views_block.podcasts-all in one full-width section instead of the six cards.
• config/canvas.content_template.node.podcast.card.yml drops content_padding, so the card title sits on the image's left edge the way the design has it.

Verified

On a clean build (rightup1x0xb3, built from 1.0.x without the Arabic recipe), after applying these three changes:

	Before	After
Podcasts grid	6 static cards, 1 linked	7 real episodes, all linked
View block	LoaderError, never rendered	renders
Card title vs image edge	24px indent	0px, flush
Card title	20px	24px (Figma Desktop/Heading/H3)
Console errors	—	0

Accessibility, axe-core 4.10.2 over wcag2a, wcag2aa, wcag21a, wcag21aa, wcag22aa: 0 violations, 25 passes on the listing. Measured separately, because axe cannot check them: no interactive target under 24x24 (2.5.8), and card text contrast 15.5:1.

Design reference: Podcast Landing Page, node 13095:6044.

Not in this MR, found while testing and worth their own issues: every podcast episode shares one featured image, and the view adds a "Shown episodes" header and a "Subscribe to Podcasts" footer the design does not have.

Checkpoints:

• File an issue
• Addition/Change/Update/Fix
• Testing to ensure no regression
• Automated unit testing coverage
• Automated functional testing coverage
• UX/UI designer responsibilities
• Readability
• Accessibility
• Performance
• Security
• Developer Documentation
• User Guide Documentation
• Reviewed by human
• Code review by maintainers
• Full testing and approval
• Credit contributors
• Review with the product owner
• Release notes snippet
• Release