Foreman Maintain

This came up as part of #33281, but it's a bit broader.

Right now, foreman-maintain doesn't run the Installer after the data has been restored.
That means that if the user has created the system not exactly as it was before, you end up with a potentially broken system.

The docs (https://docs.theforeman.org/nightly/Administering_Red_Hat_Satellite/index-foreman-el.html#restoring-from-a-full-backup_admin) say "The Foreman instance must have the same host name, configuration, and be the same minor version (X.Y) as the original system.", but that (IMHO) doesn't imply that the installer was run with all the correct parameters.

Example:
the user has a foreman with foreman_ansible installed, after restore, they forget to pass --foreman-plugin-ansbile to the installer, which results in no foreman_ansible package being installed.
now you restore the backup, which references ansible things, and foreman doesn't start anymore as ansible-related models aren't present (as ansible related code isn't there).