In many cases it would be very helpful to see what storage layout will Anaconda try to create, as that can be very useful to debug any issues later on. That could be either due to the following storage layout creation failing or the layout being too small, using incorrect filesystem, etc.

This information can be already manually reconstructed from the very verbose Blivet logs, but this process it tedious and error prone.

Additional, after a successful partitioning, we should also log the results if a lsblk call, to capture the final state of the on-disk layout. There is already a lsblk call captured in the logs from the initial scanning Blivet does, so we could use those two data points to easily compare the storage state before and after Anaconda partitioning the storage.

Overall this should be quite easy to do & provide nice benefits when debugging many issues.