Comment 1 for bug 1881588

Reproduced with uc20 + console-conf from core20 snap. Adding a subiquity bug since there are some bugs with subiquity here. Namely, `snap create-user` actually works fine in this state, I added `dangerous systemd.debug-shell=1` to the kernel commandline for the uc20 VM, and got a root shell and manually ran `snap create-user` and it worked fine.

I think the main bug here is that console-conf is incorrectly detecting that a user was created previously. However, some additional bugs I see from this situation which may or may not be worth investigating or fixing since they only really arise because console-conf incorrectly thinks there is a user:

* after getting to the "This device is registered to ..." page, the email address is blank, i.e. it verbatim says "This device is registered to ."
* hitting enter on the "This device is registered" page brings you back to the start of console-conf where it says "Press enter to configure"

Also I double checked and when the lxd user is added via seeding like this, before manually creating my own user, `snap managed` returns false, while after creating a user normally through `snap create-user`, `snap managed` returns true, so perhaps that's the check that console-conf should do to see if it should prompt the user to create a user account on the system.