[N1QL RBAC] Difference in display of generic permissions when given via n1ql vs UI

1. create 3 buckets default,test and TEST2.
2. create a user johnDoe8 with role as query_select on default and test.
3. Add another role via curl as:
curl -u Administrator:password http://172.23.98.114:8093/query/service -d 'statement=GRANT query_select on default,test,TEST2 to johnDoe8'
{
"requestID": "e96539e2-4774-41e3-9a66-fc2f4915f8ed",
"signature": null,
"results": [
],
"warnings": [

{"code":5260,"msg":"User johnDoe8 already has role query_select(default)."}

,

{"code":5260,"msg":"User johnDoe8 already has role query_select(test)."}

],
"status": "success",
"metrics":

{"elapsedTime": "44.46315ms","executionTime": "44.344102ms","resultCount": 0,"resultSize": 0,"warningCount": 2}

}

4. The role gets added correctly.Now add cluster_admin to the same user via curl:
prernamanaktala@MacBook-Pro testrunner $ curl -u 123\$#:password http://172.23.98.114:8093/query/service -d 'statement=GRANT cluster_admin to johnDoe8'
{
"requestID": "709368e3-7a8c-404d-9c62-3b4c0cfe2a2e",
"signature": null,
"results": [
],
"status": "success",
"metrics":

{"elapsedTime": "42.525235ms","executionTime": "42.480241ms","resultCount": 0,"resultSize": 0}

}

5. The UI shows all roles for johnDoe8 as shown in attachment-1.
6. Edit the Roles via UI and select cluster_admin for johnDoe8.
7. The UI shows only cluster_admin for johnDoe as shown in attachment-2.

Attachment-2 is better display of roles since user with cluser_admin role is superset of query_select role.

This bug is to remove the difference between attachment-1 and 2.