docs: refresh Divine org profile README

[rabble-claw]

Summary

Updates the org profile README to reflect current Divine branding, architecture, and active repositories.

What changed

• Replaced outdated diVine naming with Divine
• Updated repo map to current core services and apps
• Added explicit deprecation note:
  • divine-cdn-worker is deprecated and replaced by divine-blossom
• Removed stale/obsolete architecture wording and tightened contribution guidance

Why

The current org README was out of date and could mislead contributors (and LLM-assisted workflows) about active repos and architecture direction.

[NotThatKindOfDrLiz]

Closing this PR — the updates it proposed have already been incorporated (and expanded on) in main.

What happened

This branch was opened on March 7 to refresh the org README: fix branding (diVine → Divine), update the repo map, and note the divine-cdn-worker deprecation. Since then, commit 7863ea9 on main landed a more comprehensive version of the same overhaul.

Why not merge

Merging this PR would actually regress the README. The current main version includes:

• ~30 repos with tech stacks, deployment URLs, and descriptions (vs. ~15 in this PR with no stacks)
• Full architecture tables organized by category (Frontend, Core Backend, Trust & Safety, Edge & Infra, Libraries & SDKs)
• Detailed "How It Works" sections covering Nostr protocol, Blossom media storage, C2PA Content Credentials, and Keycast authentication (vs. a 4-bullet summary)
• Development setup instructions for web, mobile, and Rust services
• Repos this PR drops entirely: divine-space, divine-inquisitor, divine-relay-sync, funnel, divine-realness, social-media-age-rules-db, divine-name-sync, divine-identify-verification-service, divine-github-actions, keycast_flutter_demo, c2pa-flutter, c2pa-rs, media-kit, divine-resurrection, brand-guidelines

The PR also has merge conflicts with the current main branch, which would need to be resolved before merging regardless.

One thing worth keeping

The explicit deprecation note for divine-cdn-worker → divine-blossom is not currently called out on main. If that's still relevant, it could be added as a small follow-up.