Investigate module obsoletes/EOL handling

[jlebon]

There's an f36 change which details support for obsoleting or EOL'ing module streams:

https://fedoraproject.org/wiki/Changes/Module_Obsoletes_and_EOL

Specifically,

• for obsoleted modules, dnf system-upgrade automatically replaces the obsoleted stream by the obsoleting stream
• for EOL'ed modules, dnf system-upgrade IIUC will simply drop it from the enabled modules list

We should determine how we want to handle this in rpm-ostree. I'm somewhat leaning on not automatically doing any replacements or disablement, but instead error out (as we would today anyway) with a clearer error message, e.g.

$ rpm-ostree rebase fedora/37/x86_64/silverblue
...
error: failed to find module nodejs:11: Module stream nodejs:11 is no longer supported. It is recommended
to switch to nodejs:12

(That final bit of the error message comes from the message field of the modulemd-obsoletes.)

E.g. in the cri-o case, I don't think it's safe to automatically move cri-o versions.

[dustymabe]

I'm somewhat leaning on not automatically doing any replacements or disablement, but instead error out (as we would today anyway) with a clearer error message

👍