fix: Add 'name' tag to NIP-78 events for relay compatibility

ISSUE: shu01.shugur.net relay rejecting cart events
Error: 'NIP validation failed: application-specific data must have name field'

FIX: Added ['name', 'Culture Bridge Settings'] tag to event structure

NIP-78 Compliance:
- Some relays require a human-readable 'name' tag
- Helps relays categorize and display application data
- Standards compliance for better relay support

Event structure now includes:
- ['d', 'culture-bridge-settings'] - identifier
- ['name', 'Culture Bridge Settings'] - human-readable name (NEW)
- ['p', userPubkey] - user reference
- ['t', 'culture-bridge'] - discovery tag

Author: psam21

src/services/nostr/NostrEventService.ts

@@ -456,9 +456,10 @@ export class NostrEventService {
 
       const now = Math.floor(Date.now() / 1000);
 
-      // Base tags: d tag (NIP-33), pubkey reference, and discovery tag
+      // Base tags: d tag (NIP-33), name, pubkey reference, and discovery tag
       const baseTags: string[][] = [
         ['d', 'culture-bridge-settings'], // Single d tag for all app settings
+        ['name', 'Culture Bridge Settings'], // Human-readable name (required by some relays)
         ['p', userPubkey], // User's pubkey (required by some relays)
         ['t', 'culture-bridge'], // Discovery tag
       ];