Document authorizations necessary for GetOrganizationsApi, GetBucketsApi, GetAuthorizationsApi

Issue raised by @alksinflux

> Do these require the admin token?
> GetOrganizationsApi().FindOrganizationsAsync()
> GetOrganizationsApi().CreateOrganizationAsync()
>
>
> GetBucketsApi().CreateBucketAsync()
> GetBucketsApi().FindBucketByNameAsync()
> GetBucketsApi().DeleteBucketAsync()
>
> GetAuthorizationsApi().CreateAuthorizationAsync()
> GetAuthorizationsApi().FindAuthorizationByIdAsync()
> GetAuthorizationsApi().DeleteAuthorizationAsync()

from @russorat

> creating organizations requires the operator token, which isn’t available for users in cloud 2. Buckets API requires all access token, Authorizations requires all access token. They can quickly see the permissions for each token in the UI. Notice this all access token only has READ access to Orgs (so create org won’t work, find orgs should work but should only show my current org). It also has authorizations access, so it can create new tokens but those tokens can’t have more perms than the token that created it, so they can’t create an operator token.