Settings page should provide actionable account controls

[jamilahmadzai]

Parent bounty: #743

Bug

The /settings route currently shows placeholder copy instead of useful account controls.

Users should be able to see a clear, static overview of account/profile, notification, security, and billing or payout preferences.

Impact

• The settings route currently feels unfinished.
• Users cannot quickly inspect account visibility, notification preferences, security posture, or billing/payout defaults.
• Important account state is not scannable from the settings page.

Expected behavior

The /settings page should render a static but actionable settings overview matching the existing frontend style.

It should include sections for:

• Account / profile
• Notifications
• Security
• Billing / payout preferences

The implementation should use mock data only and should not change API behavior.

Scope

• Replace the placeholder settings card with a useful static settings overview.
• Add status chips and next-action controls.
• Keep the change scoped to apps/web/app/settings/page.tsx and shared page styles only if needed.
• Do not change backend/API behavior.

This issue is limited only to the creator of this issue. This means that only the issue author can attempt to solve this issue. If you would like to work on it, please create another issue with the same contents and refer to issue #743 for more information.

Refs #743.