Foreman Maintain

Fixes #20848 - Fix error messages indentation

Simplify the dependency graph

When composing the dependency graph for tsort, use just the collection
it was set to, instead of using resolver to find the classes by label.

Besides simplification, it also preserves the order in which the steps
were added, otherwise, the order was dependent on the Ruby version (and...

Support for run_once procedures and repositories setup

Rollback support if the upgrade fails soon enough

Support for scenario serialization/deserialization

Extract control flow of upgrades to special file

Introduce run_strategy for scenarios

Health-check scenarios are better to run all steps regardless of errors
(:fail_slow strategy), while the migration scenarios should fail as soon
as first failure happens (:fail_fast strategy).

By default, the scenarios are treated as `:fail_fast`.

Full upgrade scenario

This commit intoroduces more structured upgrade scenario consisting of
this scenarios:

• pre_upgrade_check - non-modifying checks: is the system ready?
• pre_migrations - modifying procedures before source update
• migrations - source update and main migrations...

Define order using ruby TSort

1. Introduce 2 metadata: 'before' and 'after'
2. Current order is:
Checks::SyncPlans::WithEnabledStatus
Checks::DiskSpeedMinimal
Checks::SystemRegistration
Checks::ForemanTasks::NotPaused
Checks::ForemanTasks::NotRunning
Checks::ForemanTasks::Invalid::CheckOld...

Tests for preparation steps