Add default upgrade_paths generation

[fernflower]

For POC leapp.conf will store basic information about possible upgrade_paths. Maybe will move to some other place later.

[github-actions[bot]]

Thank you for contributing to the Leapp project!

Please note that every PR needs to comply with the Leapp Guidelines and must pass all tests in order to be mergable. If you want to re-run tests or request review, you can use following commands as a comment:

• leapp-ci build to run copr build and e2e tests in OAMG CI
• review please to notify leapp developers of review request
• /packit copr-build to submit a public copr build using packit

Please open ticket in case you experience technical problem with the CI. (RH internal only)

Note: In case there are problems with tests not being triggered automatically on new PR/commit or pending for a long time, please consider rerunning the CI by commenting leapp-ci build (might require several comments). If the problem persists, contact leapp-infra.

[centos-ci]

Can one of the admins verify this patch?

[fernflower]

@pirat89 We can make it a leapp-repository specific config file then.

[fernflower]

In the framework, only the generic solutions are expected. We do not expect to install some upgrade_paths notes when people are going to convert. THe logic about upgrade paths has to be purely just in the leapp-repository located.

The framework will be used for 2 things - conversions and upgrades. I suggest we add a dedicated section about 'upgrades' to the leapp config where all upgrade-only-specific config file references go, like upgrade_paths.

The latest commit should give you the idea what I mean.

[pirat89]

closing regarding the discussion.