fix(content): resolve abutting nostr tags and suppress bech32 hyphenation

[dmnyc]

Closes #248
Closes #316

Summary

• Case-sensitive bech32 bodies (ContentParser) — wraps bech32 body patterns in (?-i:…) so the outer .caseInsensitive flag no longer lets [a-z0-9] absorb uppercase letters abutting a URI (e.g. nostr:nprofile1…Bitcoin was previously swallowed into one failing token)
• Progressive-trim fallback (ContentParser) — when a token fails bech32 checksum, trims one character at a time from the end until the prefix validates; recovers the first valid entity from concatenated bech32 strings (two nprofile URIs run together with no separator) and silently discards the broken tail
• Uppercase separator (ComposeViewModel) — the post-publish separator pass now inserts a space before A–Z in addition to a–z / 0–9, so the client itself never emits a nostr: URI abutting a capitalized word
• No injected hyphens (RichInlineTextView) — hyphenationFactor = 0 on the shared paragraph style prevents SwiftUI from breaking unresolved bech32 fallback text with stray hyphens when it wraps across lines
• Pill background hugs glyphs (WispPillLayoutManager) — the composer's mention-pill chip used to extend its background rect 4pt past the last glyph on each side, which at body font size completely covered the trailing ~4pt-wide space character and made @Name has receipts look like @Namehas receipts. The horizontal inset is now 0 and vertical bumped to -2, so the chip still reads as a rounded capsule but adjacent spaces render visibly outside it.

Screenshots

Reference event: nevent1qqsqqq9tsx4ws23w7x97edm7k3neud6uz422yqhjg62zzlagazzr0gcprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqgsr29c6mrxlzaa20qvw8q63pjqjz4n46uaztg2pwsexw79z4hnxywsv9x052

Before

After

Test plan

• Search for benchmark note nevent1qqsqqq9tsx4ws23w7x97edm7k3neud6uz422yqhjg62zzlagazzr0gcprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqgsr29c6mrxlzaa20qvw8q63pjqjz4n46uaztg2pwsexw79z4hnxywsv9x052 — first mention resolves to @mention, no raw bech32 visible, no injected hyphens
• Compose a note mentioning a user whose display name starts with an uppercase letter typed directly after the pill — verify published content has a separating space
• Compose a note with two back-to-back mention pills — verify both resolve in the feed
• Find a note where a nostr: URI abuts a capitalized word — verify the mention resolves and the word appears as separate text
• Compose a note with a @mention followed by more text — verify the space between the pill and the next word is clearly visible (not covered by the pill background)