Could mock-core-configs use fedora-distro-aliases somehow?

[praiskup]

We always have to wrap new mock-core-configs with new branched Fedora around
the time of Fedora branching event (like we did yesterday). I'm curious if we could
implement some interesting feature into mock or mock-core-configs, perhaps using
the fedora-distro-aliases project, so that this is done automatically without a new
release?

[praiskup]

see also rpm-software-management/fedora-distro-aliases#9

[praiskup]

see also rpm-software-management/fedora-distro-aliases#11

[praiskup]

I'm a bit skeptical with the fedora-distro-aliases right now, it adds a single
point of failure on external online system (Bodhi) for every Mock/Copr user.
Every build (quite a lot of API queries, actually).

[praiskup]

Since everything seems to be interlinked now, note that this issue is a different RFE from #1338.
The #1338 is rather a Fedora vs. Mock's upstream communication/synchronization problem that
has rather an easy solution.

This issue #1328 is rather about solving the issue in a much more "generic" way. The idea here would
be basically to drop all the fedora-NN-* configuration files, and rely on a reliable source giving
use the necessary constants.

[praiskup]

edit: wrong issue Outage reported here: https://matrix.to/#/!rALCnapvdNTxUTuENl:matrix.org/$wlFOALMr7CPoZPpqg8DE2QCTRaPKWeOrOa6PZSVhSKQ?via=fedora.im&via=matrix.org&via=catgirl.cloud