Limiting buckets does not account for access

[jeffreyssmith2nd]

Listing buckets when using the limit option does not take into account what buckets the user has access to which leads to expected buckets not showing up.

Steps to reproduce:
List the minimal actions needed to reproduce the behavior.

1. Create 5 buckets (test1, test2 ... test5)
2. Create a new API token that only grants the user access to test4 and test5
3. Query the bucket list route with a limit of 5. You will note that no buckets are returned.

Expected behavior:
I would expect the limit option to account for which buckets a user can see and then reduce from there. If there are 10 total buckets, the user can only interact with 5, and a limit of 3 is passed, the user should see 3 of the 5.

Actual behavior:
Depending on the sort order of the buckets, in the above example the user may see anywhere from 0 to 3 buckets.

[jeffreyssmith2nd]

Additional info can also be found at #23865 (comment)

[jeffreyssmith2nd]

Additional info can also be found at influxdata/flux#5182