fix: #3616334 Correct invalid card-featured prop values so the news featured cards render

Fixes #3616334.

Problem/Motivation

All five news featured-card content templates shipped prop values that card-featured does not allow, so the whole featured-card family rendered nothing but a Twig error:

[vartheme_bs5_educare:card-featured/content_vertical_alignment] Does not have a value in the
enumeration ["align-items-start","align-items-center","align-items-end"].
The provided value is: "justify-content-center".

• content_vertical_alignment: justify-content-center — all five files. Enum is align-items-start | align-items-center | align-items-end.
• columns_sm_size: 0408 — small, medium and large. The enum uses the NN_NN form. featured_card_xlarge already carried a correctly quoted '06_06', confirming the intended form.

It stayed invisible because nothing used these view modes yet — pages hand-placed static card-featured components instead.

Proposed resolution

• content_vertical_alignment → align-items-center in all five templates.
• columns_sm_size → '04_08' in small, medium and large.
• In the medium template, match the design it renders: date above the title, title at the h5 step, date at fs-6 in text-muted so it reads as metadata rather than a second heading.

Testing

• Rendered a real news node in all five view modes: every one renders with the title present (1637 / 4120 / 4384 / 12372 / 12488 bytes), zero render errors.
• Validated the changed YAML against card-featured.component.yml's enums — all five valid.
• Homepage using the medium card: 0 RuntimeError, 0 Twig render errors.
• gitlab-ci-local: build:composer-validate PASS, validate:yaml-lint PASS (0 YAML errors). The 🧪 Automated Functional Testing job was not run locally — it needs a full site build.

AI-Generated: Yes

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