fix suggertaccout 500 limit

[Seizens]

fix suggertaccount 500 limit
AccountInfo struct add MoreAccount parameter to see if the request needs to continue
QueryBody Add Start parameter Query start position

[andygrunwald]

Hey @Seizens,
thanks a lot for the PR. At the first glance, it seems reasonable.
However, I want to check if this is somehow related to #48 and if the S parameter is a general issue or can be solved in a general way, rather than for a single endpoint.

I have limited time right now to dig into it. Please bear with me when this takes a bit of time.
Thanks again for your efforts.

[andygrunwald]

Hey @Seizens,

thanks for raising the PR.
I merged part of your code, see 101051e.

I introduced the s directly in QueryOptions, because the parameter is also supported in other cases, see list-changes for example: https://gerrit-review.googlesource.com/Documentation/rest-api-changes.html#list-changes

I hope this will work for you.

[andygrunwald]

Maybe I made an implementation mistake with 101051e because of #48

I will fix this in the next days and add proper testing.

[Seizens]

hello @andygrunwald，
thanks you !!!
I am honored that my code is useful to you .
I find group.go groupInfo will also have number limits，
you can see https://gerrit-review.googlesource.com/Documentation/rest-api-groups.html#query-groups here ， If the number of groups matching the query exceeds either the internal limit or a supplied limit query parameter, the last group object has a _more_groups: true JSON field set.

If I have time, I will also make a new PR, and i think the numbers limits will need other place .

the last , i am sorry, my english is just soso.

[andygrunwald]

Hey @Seizens,
thanks again for your involvement.

For SuggestAccount, I have implemented your change in 67c9345

For GroupInfo, I have implemented the _more_groups field in ff14d06

If you encounter other missing features, feel free to open a new issue or a Pull Request. Thanks again.