Bump to version 0.17.0-dev.644+3de725074

[Braqzen]

Disclaimer

This is my first time touching Zig and I did use AI to help me but I've reviewed every line so if there's any mistakes please let me know. I'm not trying to submit AI slop.

Overview

Bump the repo to a newer version of Zig. I've installed 0.17.0-dev.644+3de725074 which was the latest at the time.
All builds, benches and tests pass locally.

Changes

• CI
  • Bump the version from 0.15.2 to 0.17.0
• .gitignore
  • add zig-pkg/
• API changes on std
  • mainly using std.Io.package now but some places remain unchanged
  • lots of passing around of std.io
• Allocators
  • GeneralPurposeAllocator has changed to SafeAllocator
• imports
  • change from @cImport to @import("zlib");
  • updates build.zig api
• build.zig.zon
  • new hashes and pinned urls
• python client
  • Init a new client for each test to prevent crashes since we do not handle non-data frames
• benchmark
  • change debug to stdout for printing
  • parse args with iterator instead of indexing
• transport
  • some strange broken formatting
  • update to read/write using custom fn

[Braqzen]

Strangely enough version 0.16.0 and older had exact versions but with 17 it is using a specific dev build. I'm unsure how things are developed for zig (e.g. if 17 is stable then they use the semantic version instead of dev) but I could pin it to one of the specified versions here but that is a bad practice and we'd need to update it to semantic versions asap.

I guess I need more context on how zig is developed and what the correct approach is here.

[Braqzen]

Strangely enough version 0.16.0 and older had exact versions but with 17 it is using a specific dev build. I'm unsure how things are developed for zig (e.g. if 17 is stable then they use the semantic version instead of dev) but I could pin it to one of the specified versions here but that is a bad practice and we'd need to update it to semantic versions asap.

I guess I need more context on how zig is developed and what the correct approach is here.

PR is sitting for weeks. Can we discuss this so it can be completed and merged or close it?