Adjust to error messages containing repo

[m-blaha]

Solver errors now also include the repository from which the problematic
package originates.

Requires: rpm-software-management/dnf5#1464

[m-blaha]

/packit test rpm-software-management/dnf5#1464

[j-mracek]

What about to split message and when the problem is related to installed packages write something like installed package {} does not .... What do you think?

[m-blaha]

I was thinking about it - the @System repo name is a bit cryptic for a new user.
We can split SOLVER_RULE_PKG_REQUIRES according the repo into two variants of messages - ProblemRules::RULE_PKG_CONFLICTS or ProblemRules::RULE_INSTALLED_PKG_CONFLICTS.
But there are more solver rules that would need to be split. For example SOLVER_RULE_PKG_CONFLICTS would need three variants - source installed, target installed, none installed (not sure whether there can be variant where both source and target packages are installed).
I was even thinking about having only one {} placeholder in the message and filling it either with package <nevra> from <repoid> or with installed package <nevra> "submessage" but considered this variant complicated for translators - I was not sure whether splitting a sentence into multiple translation strings would correctly work for every language.

[j-mracek]

I was thinking about approach that we used in DNF4 for {RULE_PKG_INSTALLED_OBSOLETES, M_("installed package %s obsoletes %s provided by %s from %s")}, {RULE_PKG_IMPLICIT_OBSOLETES, M_("package %s from %s implicitly obsoletes %s provided by %s from %s")},.
This approach is easy for translation but requires to extend enum. The new items must be added as last items. What do you think?

[m-blaha]

I've adjusted messages for installed packages, now they say "installed package Pkg" instead of "Pkg from @System". Thanks.

[j-mracek]

/packit test rpm-software-management/dnf5#1464