gateio: update rate limit definitions

[shazbert]

PR Description

• Updates rate definitions for Gateio using docs
• Removed func declaration func GetRateLimit() request.RateLimitDefinitions as this allocates a new rate limiting system for the package when SetDefaults is called. If using as a library service and multiple instances &gateio.Gateio{} are allocated and setup (for different key usage etc or other segregation management) then there can be an issue with getting 429'd.
• Shared rate limits with websocket system for future trading integration. There are no websocket specific rate limits but you do get rate limited, see websocket/gateio: Add request functions for websocket multi-connection [SPOT] #1598 && committed change

Fixes # (issue)

Type of change

Please delete options that are not relevant and add an x in [] as item is complete.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How has this been tested

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration and
also consider improving test coverage whilst working on a certain feature or package.

• go test ./... -race
• golangci-lint run
• Test X

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation and regenerated documentation via the documentation tool
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally and on Github Actions with my changes
• Any dependent changes have been merged and published in downstream modules

[gloriousCode]

Thanks for updating the limits!

[gloriousCode]

Hello friend, would you consider this?

Sharing requesters and thus ratelimits isn't a super complex proposition, so someone using multiple exchange structs are better served running their own thing at the moment because this only affects GateIO

We're approaching the same problem in a different manner though. I would really like to see something across exchanges done.

editeroo: If you don't want to dilute this PR, do you think this is worthwhile to make a separate PR for?

[shazbert]

Yeah I was considering that but wanted to go more in depth in another PR for a request.RegisterRateLimit(exchangeStructPointer any, map[request.EndpointLimit]*request.RateLimiter) func and maybe a protected type just for exchanges. That way any future exchange package implementations don't reintroduce the whoopsie again.

1. I can add your changes to this PR for now or
2. You can open up a PR against this and I can merge or
3. You can open a PR against master once this is merged cause I am focused on other things at the moment.

let me know how you want to proceed?

[gloriousCode]

I think its something to roll out separately in a different PR. Like I'm okay without it, as per my above second snippet. Can be revisited in future and per my first snippet, isn't crazy complex to implement

[gloriousCode]

Please make it a rate limit like the others. I initially thought this rate limit wasn't defined but was instead buried. This might just be on me as a reviewer and I will fold like paper to any argument

[shazbert]

This was the only single one in docs for 1 request every 3 seconds only on withdrawal from wallet. 🤷

[gloriousCode]

tACK!

[thrasher-]

utACK, rate limit EPLs match expected endpoints; nice work on this as that is always tedious