dep: update libvaxis

[furtidev]

We wanted to update libvaxis on Ghostty but because of this bug in the Zig build system - it didn't work out (both zf and Ghostty use libvaxis as a dependency, but there are some changes to dependencies in libvaxis itself, zigimg and libxev aren't lazy dependencies anymore. And latest libvaxis collides with zf's older one). As a workaround for now, updating libvaxis on zf is the first step. Not many changes were needed, and the TUI works as expected. So, if this isn't a bother, merging would be very helpful. Thank you! I've noticed that zf only used tagged libvaxis releases in the past - so it's fine if you don't want to update to a non-tagged version.

[natecraddock]

Hmm. Looks like the ubuntu tests failed

I've noticed that zf only used tagged libvaxis releases in the past - so it's fine if you don't want to update to a non-tagged version.

Thanks for being thorough! I think this is fine to use a non-tagged version

[furtidev]

Hmm. Looks like the ubuntu tests failed

Yep. I'll have a look tomorrow.

[furtidev]

@natecraddock The test fails mostly because in the latest version of libvaxis, a lot of the types using usize are now u16 - so the numbers used in tests can't fit in that limit. I'd like to know how you'd want the tests to be done. For example, some tests try to move the cursor to a position way way bigger than the unsigned 16bit limit. The eb.cursor value is used with vaxis, and thus it needs to be a u16.

[natecraddock]

Feel free to lower that number. I wrote those tests to confirm the cursor would be clamped to the bounds of the text. Not the best tests and I'm not super picky about how you change them

[furtidev]

I had to make some changes in eb.moveCursor to deal with integer overflowing. Tests should pass now.

[natecraddock]

Thanks for this!

[furtidev]

Thank you!