Expand existing card component to include rebranded variant

## Component/pattern to amend

https://vanillaframework.io/docs/patterns/card

## Visual


## Context

We're using these increasingly across recent rebranding builds, but there's really no best practice in place for implementation. We're currently using a mixture of existing vanilla classes and some custom styles to match the design, but given that the existing card variants are barely used anymore it seems appropriate that this new variant be officially upstreamed

Start with the card pattern documentation at the linked Vanilla Framework page and compare the existing variants with the supplied visual. Trace where the current card component styles and documentation are defined; done means the rebranded variant has an established upstream implementation and documented usage consistent with the design.

Written by the indexing model from the issue text.