Print message while initial-setup is starting

[andreabolognani]

The recently-released Fedora 41 Server riscv64 images (not official composes yet) are configured, just like on other architectures, to run initial-setup during the first boot so that the user can set up a root password and so on.

This works well, but unfortunately on slow hardware there's a fairly long pause between the moment when system messages stop being displayed and when the initial-setup UI shows up. For example, when running the image as a QEMU VM on my x86_64 machine:

[  OK  ] Started crond.service - Command Scheduler.
         Starting initial-setup.service - I…tial Setup configuration program...
[  OK  ] Created slice user-0.slice - User Slice of UID 0.
         Starting [email protected]…er Runtime Directory /run/user/0...
[  OK  ] Finished [email protected]…User Runtime Directory /run/user/0.
         Starting [email protected] - User Manager for UID 0...
[  OK  ] Started [email protected] - User Manager for UID 0.
[  OK  ] Started session-1.scope - Session 1 of User root.

... approximately 70s go by ...

[  158.443742] fbcon: Taking over console
================================================================================
================================================================================

1) [ ] Language settings                 2) [x] Time settings
       (Language is not set.)                   (America/New_York timezone)
3) [x] Network configuration             4) [!] Root password
       (Connected: enp1s0)                      (Root account is disabled)
5) [!] User creation
       (No user will be created)


Please make a selection from the above ['c' to continue, 'q' to quit, 'r' to
refresh]: 

Things are a bit better on physical hardware: for example on StarFive VisionFive 2, a very popular riscv64 board, the pause is roughly 20s long. Either way, that's long enough that people will wonder if the boot process is stuck.

It would be great if there was some indication that progress is happening before the wait. Something as simple as printing out

initial-setup loading...

as soon as possible might do the trick, however I'm not familiar enough with anaconda to know how difficult implementing something like this would be, or if it's at all feasible...