Add support for Zig arrays as MySql values

[evyatark2]

I am conflicted on how to handle insufficiently-sized arrays.

In this PR, I just truncate the data to fit the array, but in Connector/C they return an error indicating that a short-read was performed.

Would like to hear your opinion on this.

EDIT: Forgot to mention that this should be used for fixed-length MySql columns (i.e. a hash of 16-bytes), so maybe it is a user error to pass an incorrectly-sized array?

[speed2exe]

@evyatark2

Thanks for submitting the PR. My preference is about the same as yours (truncating), it's a little implicit, but I guess user should expect this when they are using field with fixed sized array type, so I am fine with it. They would be on their own.

Do you mind adding test cases in integration_tests/conn.zig for scenarios including:

• len of fixed array is the same as what server returns
• len of fixed array is greater (some bytes at the end will be undefined garbage)
• len of fixed array is lesser (truncated)

Also, adding this to README.md:354 will be helpful for documentation

[evyatark2]

Sure thing! I am also working on support for std.bounded_array

[evyatark2]

Added some tests.
I can't seem to find a good place to document this feature in the README

[speed2exe]

@evyatark2 Thanks! The test looks great! I have left one comment. The Types support can be found in the last section: https://github.com/speed2exe/myzql/?tab=readme-ov-file#binary-column-types-support

[speed2exe]

LGTM

[evyatark2]

I'll create a new PR with documentation for both arrays and BoundedArrays soon

[speed2exe]

@evyatark2 PR is looks good. Do you mind resolving the merge conflict?

[evyatark2]

Done.