Consider replacing TDNF with DNF5 in deliverables (containers, etc.)

[Conan-Kudo]

Is your feature request related to a problem? Please describe.
We're adding support for Azure Linux to Mock's default distribution targets, and it turns out we cannot leverage Azure Linux containers because they use TDNF instead of either DNF4 or DNF5.

Describe the solution you'd like
I'd like to see Azure Linux replace its usage of TDNF with DNF5, as the latter is more feature rich, supported by the broader ecosystem better, and should not have a significant impact on image sizes.

Describe alternatives you've considered
We currently aren't using the containers at all, and so Mock needs to manually bootstrap the distribution environment every time, which is much slower.

Additional context
rpm-software-management/mock#1536

[reubeno]

(Aside: Firstly, thanks for integrating the support for Azure Linux in Mock! I use Mock daily and had been iterating on an Azure Linux 3.0 config (ref: #11031, #11125) that strongly matches our preexisting manifests but had to shift to other work before getting them merged into this repo. I'd love to be able to get back to this and chat with y'all about potential for aligning it with the config in upstream mock-core-configs.)

Thanks for your suggestion regarding tdnf, @Conan-Kudo. We're also keenly interested in dnf5 although weren't ready to adopt it as default when we needed to finalize breaking changes for Azure Linux 3.0. In the months since then, we've been encouraged seeing Fedora 41 flip the switch to using it.

Regarding a container image, my understanding was that the main requirement is a stable, published container image that contains a ready-to-run package manager (dnf5 in this case) and builddep support. Did I get that right? Are there other requirements? I've read this doc on "container image for bootstrap" previously but I'm sure I could have missed something.

[Conan-Kudo]

Yes, that's pretty much correct.