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/40-add-contact.spec.ts

@@ -286,12 +286,6 @@ test('Copy contact to clipboard, then import ', async ({ page, context }, testIn
   // Copy contact details
   await page.getByTestId('contactCheckAllTop').click();
 
-  // // There's a crazy amount of overlap in all the userAgent values. Ug.
-  // const agent = await page.evaluate(() => {
-  //   return navigator.userAgent;
-  // });
-  // console.log("agent: ", agent);
-
   const isFirefox = await page.evaluate(() => {
     return navigator.userAgent.includes('Firefox');
   });
@@ -309,7 +303,6 @@ test('Copy contact to clipboard, then import ', async ({ page, context }, testIn
     return;
   }
 
-  // console.log("Running test that copies contact details to clipboard.");
   await page.getByTestId('copySelectedContactsButtonTop').click();
   const clipboardText = await page.evaluate(async () => {
     return navigator.clipboard.readText();