fix: ClaimView now correctly displays User #0 registration status

Fix ClaimView component to use $accountSettings() instead of $settings() to
get the current user's registration status. This resolves the issue where
User #0 appeared unregistered in ClaimView despite having isRegistered: true
in the database.

- Changed created() method to use $accountSettings() for user-specific settings
- Ensures ClaimView reads correct isRegistered value for current user
- Fixes "You posted that. false" display issue for registered users

test-playwright/testUtils.ts

@@ -49,9 +49,6 @@ export async function importUserFromAccount(page: Page, id?: string): Promise<st
 
   await page.getByRole("button", { name: "Import" }).click();
 
-  // Wait for import to complete
-  //await page.waitForLoadState("networkidle");
-
   return userZeroData.did;
 }
 
@@ -88,7 +85,6 @@ export async function importUserAndCloseOnboarding(
 // This is to switch to someone already in the identity table. It doesn't include registration.
 export async function switchToUser(page: Page, did: string): Promise<void> {
   // This is the direct approach but users have to tap on things so we'll do that instead.
-  //await page.goto('./identity-switcher');
 
   await page.goto("./account");