Misleading info from permission management commands feedback

[RealKC]

When a user/role is already added to a permission level(for example: DJ), trying to add it to DJ will say that the user/role is not found, while it should say that the user/role is already added to that permission level, something like "User/role is already DJ!"

[Shredder121]

This also annoyed me and Ruby. We wanted to add Ruby to a list, and I renamed myself so we would at least have a duplicate search result. But it looks like it skips already processed users, so it added a person that happened to fulfill the search query.

[RealKC]

Also something related to this is that ;;admin list will not list the owner and roles/members that have the Administrator permission, despite them having the ADMIN permissions(since by default owners and members/roles with Administrator permission have all bot permissions).

Possible new title for issue: "Wrong/missing info from permission management commands"?

[freyacodes]

The simple solution would be to say "No new roles and users" in place of "Nothing"

[freyacodes]

To clarify, this is not a bug. This has to do with user experience.

[schnapster]

This issue is partly solved in #331.

This is what's left:

Also something related to this is that ;;admin list will not list the owner and roles/members that have the Administrator permission, despite them having the ADMIN permissions(since by default owners and members/roles with Administrator permission have all bot permissions).

I wonder how this should be accomplished? I fear we would have to check each member of a guild for those permissions. What if there are many admins/(djs/users) (think 1000, just an example), how are we going to show them?