fix(input): carry key and preedit text as bytes like Zig

Zig's KeyEvent.utf8 and the embedded API's key/preedit text are byte
slices passed through to key encoding and the pty; the port converted
them lossily to UTF-8.
- KeyEvent.utf8 is &[u8] end to end (ghostty-input encoder, core,
  ghostty-lib C API, libghostty-vt key events, GTK callers). Where Zig
  validates with Utf8View (alternates, modify-other-keys, ctrl CSI-u,
  associated text, binding unicode lookup) invalid text takes the same
  "no UTF-8" fallback.
- Invalid preedit UTF-8 behaves like Zig's `try Utf8View.init`: the
  prior preedit is cleared and marked dirty, the callback returns an
  error (logged by the C API) and no preedit is set.
- The inspector key widget shows invalid key text lossily, display only.

Test Plan:
- cargo test --workspace --no-fail-fast (3407 passed)
- cargo test -p ghostty-lib --features test-platform (C-API key text
  0xff 0xfe reaches the pty unchanged)
- just check-macos (both), just check-windows, just check-wasm

crates/ghostty-apprt/src/runtime_api.rs

@@ -164,7 +164,7 @@ pub trait CoreSurface {
     // ---- input -------------------------------------------------------
     fn key_callback(&self, event: KeyEvent<'_>) -> Result<InputEffect, CoreError>;
     /// `preeditCallback(null)` clears.
-    fn preedit_callback(&self, text: Option<&str>) -> Result<(), CoreError>;
+    fn preedit_callback(&self, text: Option<&[u8]>) -> Result<(), CoreError>;
     fn focus_callback(&self, focused: bool) -> Result<(), CoreError>;
     /// Returns true if the click was consumed.
     fn mouse_button_callback(