Node: Record does not accept GlideString as a key

[adarovadya]

Describe the bug

there’s an issue with where we use Record and need to provide the option to use GlideString as the key.
Record is an object and does not accept Buffer as a key.
Usually when keys are non-primitive and needed to be store as key-val Map is the solution, we don’t think asking the user to create a map when providing input is a good UX.

Expected Behavior

Records based commands can get GlideString as a key. the expected structure should be:

[
  { key: "field1", value: "value1" },
  { key: "field2", value: "value2" },
  ...
]

Current Behavior

HSET and others Records command does not accept Buffer as a key.

Reproduction Steps

change the hset command: 
public async hset(
        key: GlideString,
        fieldValueMap: Record<GlideString, GlideString>,
        decoder?: Decoder,
---------------------------------------------------------
                const field1 = uuidv4();
                const field2 = uuidv4();
                const value = uuidv4();
                const fieldValueMap = {
                    [Buffer.from(field1)]: Buffer.from(value),
                    [Buffer.from(field2)]: Buffer.from(value),
                };
                expect(await client.hset(key, fieldValueMap)).toEqual(2);

Possible Solution

No response

Additional Information/Context

No response

Client version used

Engine type and version

OS

Language

TypeScript

Language Version

Cluster information

No response

Logs

No response

Other information

No response

[Yury-Fridlyand]

export type GlideRecord<T> = [key: GlideString, value:T][]

[Yury-Fridlyand]

Please see PoC in Bit-Quill#418

[Yury-Fridlyand]

#2207 contains fix for that issue. It is still in WIP state, because changing the approach of Record use causes a lot of changes and test fixes.
Currently it is done ~ 50% and Bit-Quill#421 adds ~30% more.
Most significant parts not done at the moment are - update docs, fixing flaky tests and adding new test.