Migration to new plymouth needs more work

When checking the commit 6b6cfff6 I see a lot of file removal. There are used hooks and scripts some of our users may have running at their systems. Also removing systemd service files might lead to broken installs for some users.

• we have to detect if any files we want to remove are used by the system
• we have to find a way to properly migrate that
• we may want to setup VM installs to mimic those installs and break them to find a working solution

Therefore we can't ship any plymouth package changes to our stable branch, unless we have a proper solution to not break systems on package update.

Last known working plymouth package: 22.02.122-15 We can adopt the changes made to the watermark shown in revision 16. Other changes need more review from our end.