The path with "active-theme" are already "managed" by desktop-base
and we don't want an install+removal of desktop-base to mess with the
alternatives that we have setup in kali-desktop-base.
Restore the removal code for alternatives that were voluntarily shared
with desktop-base.
We divert plymouth's configuration file to install our version
configuring the kali theme. Stop using the plymouth-set-default-theme
in kali-desktop-base.
In prerm, don't drop the alternatives going through "active-theme" they are
the responsibility of desktop-base. In postinst, continue to create them
to update them in case the new kali theme provides the file that the
former theme did not.
Fix the check protecteding the call to plymouth-set-default to use a
version that actually existed in kali-themes even though we don't really
have an upgrade case where we wanted to call the command. But it will
make it easier to force a re-run in the future, in case we change the
name of the plymouth theme.
