Fix Pimcore bundle installation order and repair legacy state

[kingschnulli]

Summary

• install DataHub, Data Importer and application bundles before the global Doctrine migration pass
• repair existing runtimes where historical bundle migrations marked DataHub/Data Importer installed before their installers ran
• rerun the real bundle installers only when their installer artifacts are missing
• clear the Studio studio_backend_user_permissions cache after a repair
• add a regression test for setup ordering

Why

Historical DataHub/Data Importer migrations can set their BUNDLE_INSTALLED__... settings before the bundle installers run. The normal pimcore:bundle:install command then exits early as already installed, leaving installer-only side effects missing, including plugin_datahub_config and the Application Logger installation.