Fix type hinting of zrange and zrangestore

[aveao]

Pull Request check-list

• Do tests and lints pass with this change?
  • locally tested, yes
• Do the CI tests pass with this change (enable it first in your forked repo and wait for the github action build to finish)?
  • Yes
• Is the new or changed code fully tested?
  • Runs fine, and this is only typing changes
• Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
  • Unsure if I see any related documentation, the docstring was already correct.
• Is there an example added to the examples folder (if applicable)?
  • Not applicable

Description of change

Fixes #252

start/end are type hinted as int only, whereas when bylex (or byscore) is set to True, the value is expected to be prepended with [ or (, as stated both in the function's docstring and redis docs.

This can only be done if start/end are passed as a string or as bytes.

Equivalent to redis/redis-py#3872

[mkmkme]

Hey! Thanks for your PR. I'm currently working on the bigger change related to typing system in the repo. It's quite a mess at this point. My changes will make your changes obsolete. We can of course merge this one, but there won't be a lot of sense to keep it soon

[mkmkme]

Hey! I've landed quite a large change recently to valkey/commands/core.py, and now these changes should be also propagated to the Sync and Async overload of those functions. That's nothing major -- your changes simply need to be applied at the same file in several other places.

Do you want to do it yourself in your PR or do you want me to do it separately?

Anyways thanks for calling this out, that's a good catch!