🐛 Installing fails if user account is named "algorand"

[SilentRhetoric]

Describe the bug
A fresh NodeKit install on Ubuntu in which the user account was already named algorand failed to install properly and did not produce a meaningful error.

To Reproduce
Steps to reproduce the behavior:

1. With a Linux user account algorand
2. Install NodeKit
3. FATA: algod is not running

Expected behavior
NodeKit could detect the user account and throw a descriptive error.

Screenshots

Additional context
User was able to build a new image with a different user account name and NodeKit worked fine.

[tasosbit]

Default systemd service runs algod with user=algorand - very likely related

We'll see what we can do. Worst case scenario we just warn people who have this username

[tasosbit]

We are unlikely to be able to do something about this, as we don't want to delve into "changing systemd service file" territory.

@dliptak001 The fix I would recommend is to rename the user account AND group from algorand to algo

@PhearZero implementation note: we should warn when we detect this, but need to take care not to confuse a service algorand user (uid < 1000) with a regular algorand user (uid >1000)