Rework transaction response handling in glide core and all clients

[Yury-Fridlyand]

Describe the feature

Glide receives response for all commands in a transaction, but ignores all of them if an error present and returns that error (only the first error if there are multiple of them). It should return all responses along with all errors received.

Use Case

127.0.0.1:6379> multi
OK
127.0.0.1:6379(TX)> get 1
QUEUED
127.0.0.1:6379(TX)> get hash
QUEUED
127.0.0.1:6379(TX)> ping pong pang
QUEUED
127.0.0.1:6379(TX)> exec
1) (nil)
2) (error) WRONGTYPE Operation against a key holding the wrong kind of value
3) (error) ERR wrong number of arguments for 'ping' command

Proposed Solution

No response

Other Information

This feature may depend on tuple type support #1188

Acknowledgements

• [X] I may be able to implement this feature request
• [X] This feature might incur a breaking change

Client version used

N/A

Environment details (OS name and version, etc.)

N/A

[nihohit]

related: https://github.com/redis-rs/redis-rs/pull/1093 once Value::Error is added, the transaction response can be a Vec<Value>, and the core can decide whether to pass errors or fail.