fix: revalidate /customize (not /settings) after customize-panel mutations

The invites/onboarding/areas/roles/tiers admin panels moved to /customize, but
their actions still revalidated the old /settings route, so the /customize
Router Cache went stale after a write. Point them at /customize (keeping the
other cross-page revalidations).

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>

lib/actions/tiers.ts

@@ -39,7 +39,7 @@ export async function createTier(input: {
     .single()
 
   if (error) return { error: error.message }
-  revalidatePath('/settings')
+  revalidatePath('/customize')
   return { id: data.id }
 }
 
@@ -76,7 +76,7 @@ export async function updateTier(tierId: string, updates: {
     .eq('space_id', member.space_id)
 
   if (error) return { error: error.message }
-  revalidatePath('/settings')
+  revalidatePath('/customize')
   return { success: true as const }
 }
 
@@ -98,6 +98,6 @@ export async function deleteTier(tierId: string) {
 
   if (error) return { error: error.message }
   if (count === 0) return { error: 'Cannot delete a built-in tier. Archive it instead.' }
-  revalidatePath('/settings')
+  revalidatePath('/customize')
   return { success: true as const }
 }