Node: Handle commands with binary output in transaction

[Yury-Fridlyand]

1. Added option for a command in a transaction to require binary decoder
2. Added check for this in exec calls
3. Added IT for that feature
4. Fixed docs for exec
5. Added client.close() in IT where it was missing
6. Reworked shared tests (pair of runBaseTests and runCommonTests) to accept client config and redefine params
7. Removed unused context from shared tests

Should be merged before #2126 and #2129

[yipin-chen]

There is a CI failure related to your changes.

[Yury-Fridlyand]

Can't reproduce it locally, but I fixed that.

[jonathanl-bq]

Suggested change

	* Node: Added handlind commands with binary output in transactions ([#2133](https://github.com/valkey-io/valkey-glide/pull/2133))
	* Node: Added handling for commands with binary output in transactions ([#2133](https://github.com/valkey-io/valkey-glide/pull/2133))

[acarbonetto]

I think we should align more closely with the Java implementation. I'd suggest that we move the Decoder from the exec() call to the Transaction object. The user can set the decoder (optionally) when creating the Transaction object, or by calling something like .withBinarySafeOutput() like we do in Java.
In this case, exec() would only take a transaction object.
Reference: https://github.com/valkey-io/valkey-glide/pull/1814/files#diff-a9af498f347847324483b3ee806c7a98babbfba5ff1313c7998edecdc652aa5a

[acarbonetto]

Suggested change

	"Transaction has a command which requres `Decoder.Bytes`.",
	"Transaction has a command which requires `Decoder.Bytes`.",

[acarbonetto]

Maybe:

"Pass decoder=Decoder.Bytes as part of the exec() command to process transactions that return Bytes."