Migration tasks should not do global config updates on content-apps but rather be run in each module. This is a cleaner approach since module devs have to change the bootstraps anyway.

The goal is that each module takes care of itself, then we have a clear path for migration: e.g. add the following 3-4 UI tasks to your MVH and update your bootstrap files.

This epic is about propagating these migration tasks to all affected modules, so that their content apps run smoothly on Magnolia 5.3.

This also requires clear documentation on how to upgrade a module, including API changes, config/bootstrap updates, migration tasks to add to MVH.