Fix CLIENT TRACKING command format for multiple prefixes

[philippzagar]

When using CLIENT TRACKING with multiple prefixes, the generated Valkey command has invalid syntax.

The current implementation works fine for a single prefix, but fails with multiple prefixes. Valkey expects the format PREFIX prefix1 PREFIX prefix2 (each prefix needs its own PREFIX keyword), which causes a syntax error with our current approach.

See: valkey.io/commands/client-tracking/

[philippzagar]

@adam-fowler @fabianfett Please approve the CI and review the PR once you have the chance

[adam-fowler]

This won't be the fix. You are editing generated files. Your changes will get overwritten the next time we run the code generator.

There is a chance this is a general issue with arrays and prefixes. I will investigate

[philippzagar]

You are editing generated files

Totally didn't notice that, thanks!

general issue with arrays and prefixes. I will investigate

Yes, seems like there is an issue in the generator then.
Feel free to use the tests that I wrote for this specific CLIENT TRACKING behavior in your fix then.

[adam-fowler]

Yes, seems like there is an issue in the generator then.

I found a new tag in the json model files multiple_token. It looks like this indicates arrays with a token being rendered TOKEN entry1 TOKEN entry2 ....

[philippzagar]

Yes, seems like there is an issue in the generator then.

I found a new tag in the json model files multiple_token. It looks like this indicates arrays with a token being rendered TOKEN entry1 TOKEN entry2 ....

Great! Will you put up a PR for the generator that respects this?

[adam-fowler]

#269