Resolves #6030
Impact: breaking|major
Type: feature|refactor

Issue

We'd like to move away from the all encompassing "owner" role.

Solution

• remove the code which adds users to an "owner" role when creating an account
• remove code which adds user to "customer" role when creating a non-owner account, users no longer are required to be in a group
• add code which adds first use to system-manager and accounts-manager GLOBAL groups, and also creates those groups if they do not already exists
• removes default creation of guest and customer groups
• remove restriction of inviting user to owner group (meaning we can have more than one owner)
• remove isOwner logic from canAddAccountToGroup, and leave only policy validation
• remove owner "override" in hasPermissions
• remove any code related to owner permissions that should no longer be there

Breaking changes

• owner is no longer a permission. Since this permission was basically a key to do anything in the app, if you had custom code that was passing owner for permission checks, you'll need to update to make sure the user has more specific permissions

Testing

• make sure all places where "owner" was being used as the permission still work with more specific permissions