FEATURE rueidislimiter: Introduce RateLimitOption to RateLimiterClient

[altanozlu]

Currently it's not possible to use instance of RateLimiter and share it with different use cases.

[rueian]

Suggested change

	type RateLimitOption func(*RateLimit)
	func WithLimit(limit int) RateLimitOption {
	return func(rl *RateLimit) {
	rl.limit = limit
	}
	}
	func WithWindow(window time.Duration) RateLimitOption {
	return func(rl *RateLimit) {
	rl.window = window
	}
	}
	type RateLimitOption func(RateLimit) RateLimit
	func WithLimit(limit int) RateLimitOption {
	return func(rl RateLimit) RateLimit {
	rl.limit = limit
	return rl
	}
	}
	func WithWindow(window time.Duration) RateLimitOption {
	return func(rl RateLimit) RateLimit {
	rl.window = window
	return rl
	}
	}

Hi @altanozlu, we can have better performance and fewer allocations with the above change.

Also, is there a case we want to adjust only one of the limit or window? If no, we should probably merge these two WithLimit and WithWindow.

[altanozlu]

Hey, went into another route and changed RateLimitOption as a struct, since nothing is exposed to user, changing it into something else (e.g. type RateLimitOption func(RateLimit) RateLimit) shouldn't be a problem in the future.
Now there is only 1 extra allocation when RateLimitOption is used.
It might be a little unorthodox so let me know if I should stick to conventional option usage.

[rueian]

This one looks good to me. Thanks @altanozlu!