Roles are for services not for users. If you have a read-only Web api then it makes sense to use a read-only role regardless of which user is using it.
It's just named such that when a ROLE allows `login` it's considered a user
Might as well simplify the mental model and make them the same.
All roles function like you would expect groups to function
A role that is not allowed to login is a `group`.
While the CREATE USER and CREATE GROUP commands still exist, they are simply aliases for CREATE ROLE.