One un-instantiable applied recipe blanks the entire catalog

Problem

When a recipe source (e.g. a custom recipe catalog) lists recipes, opening the catalog can return an empty list / HTTP 500 with no indication why. A single applied recipe whose shipped config has diverged from active config is enough to take down the *whole* listing - you end up with a blank page.

Root cause, generated with AI-help: `Normalizer::getActivationInfo()` calls `$activator->getTasks()` (and `getInstructions()`) without catching exceptions. For an Active recipe, `RecipeActivator::getTasks()` calls `Recipe::createFromDirectory()`, which instantiates core's `ConfigConfigurator` and throws `RecipePreExistingConfigException` whenever the recipe's shipped config no longer matches the live config.

Core throwing here is reasonable: `createFromDirectory()` is strict by design (see core #3570467, #3446329). The bug is that Project Browser lets that throw propagate and blank the catalog instead of degrading the one affected project.

Proposed resolution

Catch the exception, log a warning, but render the rest of the list.