RFE: Support for susedata.xml in repodata

[Conan-Kudo]

Zypper supports an extension to rpm-md known as the susedata.(lang.)xml file.

This extension offers a number of extra attributes, as noted here:

• https://github.com/rpm-software-management/rpm-metadata/blob/main/historical/suse/yum-schema/susedata.rnc
• https://github.com/rpm-software-management/rpm-metadata/blob/main/historical/suse/yum-schema/susedata.rng

This extra repodata file offers two main properties:

• A way to ship proprietary licenses for packages that need explicit user agreement via the EULA tag when the package is requested (susedata.xml)
• A way to ship translations of RPM tags (in susedata.$LANG.xml)

In order to make it possible for SUSE distributions to ship DNF instead of Zypper, we need this data handled if it exists in the repodata, and support for signaling EULA stuff out to frontends (e.g. PackageKit, which does support this with the Zypp backend too).

This would also be useful for Fedora, particularly the ability to handle proprietary licenses, since this facility is required to be able to accept EULAs for software pre-transaction without requiring horrible hacks (e.g. Microsoft SQL Server ODBC driver RPMs use a preinstall script to force acceptance of the EULA, and rejecting it breaks your system).

(Migrated from RHBZ#1908373)

[Conan-Kudo]

Sample metadata files:

• Example susedata.xml from openSUSE Tumbleweed non-oss repo
• Example susedata.es.xml from openSUSE Tumbleweed non-oss repo

[Conan-Kudo]

FYI @dcantrell @dmach @lkocman

[m-blaha]

This is valid request. Currently the metadata types libdnf5 knows about are hardcoded (see include/libdnf5/conf/const.hpp). We should think of more flexible way how distributions (or API users) can define their own set of repository metadata.

Related: #1564