Fix Clerk profile routing and handle users without organizations

Resolved Clerk routing conflicts for profile pages — Added hash-based routing for Clerk profile components so Clerk's internal navigation no longer conflicts with Next.js path routing. This avoids requiring catch-all routes and prevents navigation errors for users.

Added routing="hash" to OrganizationProfile and UserProfile so Clerk uses hash-based navigation and does not conflict with Next.js path routing.frontend
Updated the organization settings page to guard against missing organizations: when no org is active the page displayed a CreateOrganization prompt instead of failing to render.auth
Removed the mandatory redirect to /app/onboarding when a user had no organization; users now land on the dashboard and projects are shown for their user account.frontend
Scoped project queries to the user when no organization is active (owner_type = 'user'), preventing errors and ensuring users see their own projects.backend