fix: CORS + CORP + inline disposition on public banner image responses
Some clients (including possible Bluesky composer fetch paths) validate
og:image via cross-origin fetch rather than plain <img>. Add
Access-Control-Allow-Origin: *, Cross-Origin-Resource-Policy: cross-origin,
and Content-Disposition: inline on /api/registry/banner and /og-banner.
Made-with: Cursor