Frontend Touch ups: UI/UX, A11y, Responsiveness and Performance

[abayomicornelius]

This PR addresses multiple frontend issues to improve the overall user experience and align with the Drips Wave theme.

Changes:

• Onboarding Flow ([Frontend] Touch up: Align color palette in Onboarding Flow #556): Aligned color palette with the Drips Wave theme and added subtle animations.
• Sidebar Accessibility ([Frontend] Touch up: Fix accessibility (a11y) issues in Sidebar #538): Improved semantic structure using lists and added aria-current attributes.
• Transaction Table Responsiveness ([Frontend] Touch up: Improve mobile responsiveness of Transaction History Table #540): Added a mobile-first card view for better usability on small screens.
• Wallet Modal Performance ([Frontend] Touch up: Optimize rendering performance in Wallet Connection Modal #547): Optimized rendering using useMemo and useCallback hooks.

Closes #556
Closes #538
Closes #540
Closes #547

[vercel]

@Temi-suwa18 is attempting to deploy a commit to the Emmanuel's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

@abayomicornelius 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

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
29404147	Triggered	Generic Database Assignment	c7fa15b	backend/check-db-state.js	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}