Motivation for this change

@jtojnar is getting gdm to use wayland in #39615. Trying it out I ran into a problem where gdm would fail the first time when using plymouth (on a 3rd gen X1 carbon, but not in a VM for some reason).

According to the service directory in plymouth "multi-user.target" should want "plymouth-quit-wait.service":

├── multi-user.target.wants
│   ├── plymouth-quit.service -> ../plymouth-quit.service
│   └── plymouth-quit-wait.service -> ../plymouth-quit-wait.service

This change fixed gdm running wayland, and seems like reasonable change since it's apparently expected by plymouth.

However the change made other display managers not quit plymouth properly, leaving it running in the background consuming cpu. Removing "multi-user.target" from plymouth-quit.after makes plymouth quit as expected. Not sure why having it there was a problem though.

cc @abbradar (sorry for bugging you) as he's the author of the code I'm changing.

Things done

Tested all the display managers in a VM. All are showing the console on stage 1. as expected (I'm assuming this is needed for LUKS password). Also tested without xserver which also worked fine.

Though I haven't tested the configuration with LUKS enabled. If someone knows how to test this easily in eg. a VM that would be great.

• Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
• Built on platform(s)
  • NixOS
  • macOS
  • other Linux distributions
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Fits CONTRIBUTING.md.