feat(admin): use Site Identity logo/favicon as admin panel branding default

[Vallhalen]

Problem

The admin panel has two separate branding systems:

1. General Settings → Site Identity — logo, favicon, site name (already configurable from the admin UI)
2. astro.config.mjs → admin: { logo, favicon, siteName } — white-label config (new in 0.7.0)

These are disconnected. The admin panel doesn't use the Site Identity values that are already set in General Settings. Users expect that uploading a logo in Site Identity would brand the admin panel too.

Proposal

The admin panel should fall back to Site Identity values (logo, favicon, site name) when no explicit admin config is provided in astro.config.mjs. Priority order:

1. astro.config.mjs → admin: { logo } (explicit override, highest priority)
2. General Settings → Site Identity → Logo (already stored in DB)
3. EmDash default branding (current behavior, lowest priority)

This way:

• Agencies using admin config keep full control
• Everyone else gets their branding "for free" without touching config files
• No breaking change — just a smarter default

Context

As a user, I already uploaded my logo and favicon in General Settings. I was surprised the admin panel still showed EmDash branding. The data is already there — it just needs to be read.

[ascorbic]

Moving this to a Discussion in Ideas -- using Site Identity logo/favicon as admin branding is a feature proposal. Per CONTRIBUTING.md, feature requests need a Discussion before PR work.

[mikulthegreat]

I like this idea, saves a bunch of time