Avoid using panic in Redis Commands

[ofekshenawa]

In various functions within the go-redis library, there is a use of panic to handle cases.
Using panic for this purpose is not in line with Go's idiomatic error handling and can result in unexpected program termination.

Suggested Improvement:
Replace occurrences of panic with a more idiomatic error return approach. This allows users to handle argument validation errors gracefully through error checks and aligns with Go's standard error handling practices.

[SoulPancake]

Can you illustrate an example of how we can solve this?
I would like to help with this @ofekshenawa

[eidoid]

Can you illustrate an example of how we can solve this? I would like to help with this @ofekshenawa

By using a middleware to capture panics and return as error perhaps.

[github-actions]

This issue is marked stale. It will be closed in 30 days if it is not updated.

[ndyakov]

I think we can revisit the panics in go-redis and see if all of them make sense.

[SoulPancake]

@ndyakov We can cascade all errors to callers except the ones related directly with boot, where maybe a panic is the right thing to do
something like this?

[elena-kolevska]

I agree that we should evaluate every case separately and return the error to caller.

[ndyakov]

Adding this to our backlog of issues to look at.

[dragneelfps]

@ndyakov I tried hacking up a PR for this. Could you or anyone else review it? Thanks!