In Fedora 39 a new `Runtime` module got introduced [1]. The changelog notes that Anaconda will crash if this module is not enabled.

Anaconda is configurable as to which modules are allowed to be activated, or explicitly forbidden from running through files in `/etc/anaconda` (either dropins, or directly in `anaconda.conf`).

Recently I was working on a bug where we didn't have the runtime module available in `activatable_modules`. We never did this (and we didn't observe any crashes of Anaconda, FWIW), however with a PR that landed for Fedora 42 [2] the execution of `%post` scriptlets is now handled by this module which made us notice that the ISOs we build aren't correct.

This is clearly user error since it is noted in the changelog that this module should always be activated.

However, after some chats I think this could be handled more gracefully. If the intent is that Anaconda without the runtime module activated crashes (as written in the changelog) then to me it doesn't make a lot of sense that I can make it not run through configuration. Perhaps the runtime module should be activated unconditionally, no matter the configuration?

[1]: https://anaconda-installer.readthedocs.io/en/latest/release-notes.html#new-runtime-module

Reproducible: Always