see nextcloud#6

also regroup issues by type now that this list is growing a bit large

We probably need a clearer workflow for this, but it seems clear to me
those don't need to stay "standard" forever...

Closes: team#33949

Under bullseye the old command aborts with: "Failed to reload
local-fs.target: Job type reload is not applicable for unit
local-fs.target."

The restart operation seems to work, and the new .mount unit is created
as expected.

-l and -L are easy to confuse, just use --size here

Document the chroot remount procedure with environment variables instead
of hardcoding all the paths, making it easier to use this in different
hardware environments.

Also, assume that the "rebuild grub" set of commands occur within the
chroot as this is the expected result of the previous set of commands.

Permalinks ftw. Unfortuntaly, the immerda one is dead and I can't find
an alternative.

This is proving necessary to fast-track at least a proposal on this
considering the state of Python 2 in bullseye.

/cc @lavamind

For example, -n doesn't exist in zsh, and -p has a different
meaning. In general, I had to scroll through pages and pages of the
bash manpage to even figure out what does options do, so I prefer to
keep things simple and stay with a more classic "press enter to
continue".

I'm sure people can find the ENTER key if they were managing to find
the ANY key before. ;)

This will be more useful to users than the internals of the procedure.

It's basically the same as buster, again.

Instead of telling the user "when clean_conflicts asks you this, tell
it to remove those files", just remove the damn files.

That removes 13 prompts!