[Feature]: Add an property to Card for a built-in disabled state

[soulcramer]

Outcome

Card accepts an enabled parameter and handles disabled opacity and click blocking internally.

Problem

Card is a wrapper with no concept of a disabled state; callers must manually apply disabled opacity and suppress interactions, leading to inconsistent implementations across the codebase.

Context

Current behaviour: there is no enabled parameter on Card, so consumers replicate disabled logic themselves.
Source file: spark/src/main/kotlin/com/adevinta/spark/components/card/Card.kt

Scope

• Add an enabled: Boolean = true parameter to Card.
• Apply disabled visual (reduced opacity) and block clicks when enabled = false.

Acceptance criteria

• Setting enabled = false on Card renders it at the disabled opacity and ignores click events.
• A screenshot test covers the disabled visual state.
• A UI test confirms clicks are suppressed when disabled.

Evidence

• Slack: https://adevinta.enterprise.slack.com/archives/C04QQEU3Y2H/p1785405321059579 — Eliott L., 2026-07-30
• spark/src/main/kotlin/com/adevinta/spark/components/card/Card.kt — current Card implementation with no enabled parameter