We often use the fake classes in our migrations to avoid the issues with the real active record models when
the data are not migrated fully yet + some hooks might trigger orchestration.

This approach fails with `Host` and other STI objects, as it loads the class based on the `type` attribute
(see related issues).

We should provide a standard way how to do the data manipulations safely without risking unexpected issues.

Often the errors doesn't show immediately in isolation, but rather when multiple plugins are in place.