Steps to reproduce

1.  Create a decorator for a non-existing module
2.  Create a decorator for an existing module (but so that this one is applied after a previous one).

Expected results

The malicious one is not applied, while the legit one should've been picked up without a problem.

Actual results

The whole sequence of decorators is not applied. You should see an error in module startup logs.

Workaround

Explicitly get rid of the malicious decorator, much like it has been e.g. in this change for free trials that suffered after an update that has been removing ranker (FT infra was bringing in a decorator to disable ranker).

Development notes

Whether this concerns only module configs or also the "conventional" registries is not verified yet, there's a chance that those are un-affected.