Improve card visual hierarchy with varied elevations

[D-Bluemoon]

Added 3 elevation levels (elevated, default, flat) via Card component variant. Primary content cards use elevated shadow, secondary cards use default, info banners use flat. Creates clear visual hierarchy.

Description

This pull request introduces a 3-tier card elevation architecture to address layout parity issues. Previously, all dashboard sections carried identical layout structures, reducing data processing contrast. By defining structured elevated, default, and flat variant layers, primary functional metrics (like the core Revenue tracking module) gain distinct prominence via visual elevation, standard structural groupings occupy a clean uniform baseline, and secondary notification text elements blend seamlessly into the container space.

Fixes / Closes: #69

---

Type of Change

• Bug Fix (non-breaking change which fixes an issue)
• New Feature (non-breaking change which adds functionality)
• Breaking Change (fix or feature that would cause existing functionality to not work as expected)
• Refactoring / Performance (clean-up or performance optimization without behavioral changes)
• Documentation / CI (changes to docs, workflows, config files)

---

Verification & Test Plan

Automated Tests

# Executed standard workspace verify and build pipelines
npm run build

Manual Verification

1. Confirmed changing the elevation attribute on custom Card objects properly swaps underlying Tailwind ring and shadow variables.
2. Verified the primary Revenue Chart module highlights perfectly on the layout panel with a higher depth rating.
3. Inspected the bank configuration notification banner component to ensure it scales cleanly using the flat dashed parameter layout.

---

Sub-System Checklist

1. Smart Contracts (BettaPay-Contract)

• Code compiles without warnings (cargo build --release --target wasm32-unknown-unknown)
• Cargo test suite passes locally (cargo test)
• Emits events for state changes
• Implemented proper authorization controls (auth.require_auth())

2. Backend Services (BettaPay-Backend)

• Prisma models updated and migrated (if database schema changes)
• Zod validation checks added/updated
• API routes and services build successfully (pnpm build)
• Local env variables updated in .env.example

3. Frontend Dashboard (BettaPay-Frontend)

• Local build completes successfully (pnpm build)
• Focus states, labels, and aria attributes tested for accessibility
• No regression on styling or components
• Env parameters documented in .env.local

---

Checklist

• My code follows the style guidelines of this project (run formatters/linters)
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings

[vercel]

@D-Bluemoon is attempting to deploy a commit to the therealjhay's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

@D-Bluemoon Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits