fix(fetch-service): parallelize NIP-05 verification in fetchProfile

[userAdityaa]

Description

This PR parallelizes NIP-05 verification in fetchProfile. Previously, each call to verifyNip05Identifier was awaited inside a loop, causing serial blocking. Now, all NIP-05 checks run concurrently, so the UI is responsive and cached profiles display immediately. The early context update is restored, and NIP-05 badges still appear once verification completes. Profiles without a nip05 field are unaffected.

Before: N × 10 s (serial, each blocks the next)
After: 1 × 10 s (parallel, all run together, capped at the slowest single host)

Fixes #352

Testing

1. Open marketplace, filter DevTools Network to nostr.json, and verify all NIP-05 requests fire simultaneously.
2. NIP-05 badges still appear after all requests settle.
3. Profiles without a nip05 field are unaffected.

Checklist

• My code follows the code style of this project
• I have performed a self-review of my code
• My changes generate no new warnings or errors

[vercel]

@userAdityaa is attempting to deploy a commit to the shopstr-eng Team on Vercel.

A member of the Team first needs to authorize it.

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

This PR improves fetchProfile responsiveness by moving NIP-05 verification out of per-event serial awaits and into a concurrent batch, while restoring an early context update so profiles can render before verification completes.

Changes:

• Added verifyProfilesNip05 helper to verify NIP-05 identifiers concurrently with Promise.allSettled.
• Updated DB and relay profile parsing to stop awaiting verifyNip05Identifier inside loops.
• Restored early editProfileContext update and added a follow-up update after verification completes.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[GautamBytes]

LGTM

[userAdityaa]

All merge conflicts have been resolved and the commits have been squashed!