Update packit with currently supported upgrade paths

[fernflower]

That' an adoptation of leapp-repository's packit update and refactoring introduced in PR1176.

OAMG-10855

[github-actions]

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 mergeable.
If you want to request a review or rebuild a package in copr, you can use following commands as a comment:

• review please @oamg/developers to notify leapp developers of the review request
• /packit copr-build to submit a public copr build using packit

To launch regression testing public members of oamg organization can leave the following comment:

• /rerun to schedule basic regression tests using this pr build and leapp-repository*master* as artifacts
• /rerun 42 to schedule basic regression tests using this pr build and leapp-repository*PR42* as artifacts
• /rerun-sst to schedule sst tests using this pr build and leapp-repository*master* as artifacts
• /rerun-sst 42 to schedule sst tests using this pr build and leapp-repository*PR42* as artifacts

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.

[packit-as-a-service]

Failed to load packit config file:

Please correct data and retry.

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Please correct data and retry.

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Please correct data and retry.

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Please correct data and retry.

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Please correct data and retry.

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Please correct data and retry.

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[fernflower]

Hmm thats weird, packit validate is happy with the config when run locally

(.venv) [ivasilev@ivasilev-thinkpadp1gen4i packit]$ packit validate-config ../leapp/.packit.yaml 
fedpkg is not executable or in any path
2024-03-01 16:35:27.935 schema.py         WARNING The 'metadata' key in jobs is deprecated and can be removed. Nest config options from 'metadata' directly under the job object.
2024-03-01 16:35:27.935 schema.py         WARNING The 'metadata' key in jobs is deprecated and can be removed. Nest config options from 'metadata' directly under the job object.
2024-03-01 16:35:27.942 validate_config.py INFO   .packit.yaml is valid and ready to be used

[pirat89]

/packit build

[pirat89]

/packit copr-build

[pirat89]

lgtm and seems working