v4.0.11 - Theme preset persistence on standalone

Bug Fixes

• Theme preset now persists on standalone installs. ThemeManager::activeTheme() branched on the multisite session context and read via SiteSetting::getGlobal() when no context existed. On standalone installs, the save path writes to the default site's override (post-4.0.8 resolver fallback), but this branch read from the globals table — so the preset visually reverted to the theme's default on page reload, even though the override was saved correctly. Same symptom on the frontend when the cache wasn't cleared. The read now uses SiteSetting::get() unconditionally, which resolves site-aware on both standalone and multisite installs.

Test Coverage

• ThemeManagerPresetPersistenceTest — 2 tests covering the save/read round-trip and DB row location.