fix(core): use dev tty for crossterm (#30696) ## Current Behavior `git push -u origin HEAD` causes the following panic when the TUI is enabled on macos: ``` Backtrace (most recent call last): File ":0", in __pthread_cond_wait File ":0", in std::sys::pal::unix::thread::Thread::new::thread_start File ":0", in core::ops::function::FnOnce::call_once{{vtable.shim}} File ":0", in std::sys::backtrace::__rust_begin_short_backtrace File ":0", in tokio::runtime::task::raw::poll File ":0", in tokio::runtime::scheduler::multi_thread::worker::Context::run_task File ":0", in tokio::runtime::task::raw::poll File ":0", in tokio::runtime::task::core::Core::poll File ":0", in nx::native::tui::tui::Tui::start::{{closure}} File ":0", in core::option::expect_failed The application panicked (crashed). reader source not set in /Users/jason/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/crossterm-0.29.0/src/event/read.rs:39 thread: tokio-runtime-worker ``` This is due to the fact that crossterm until recently did not use /dev/tty on mac and thus could not read events correctly when forwarded from another program such as husky. ## Expected Behavior This adds the `use-dev-tty` features so that `crossterm` utilizes `/dev/tty` and works when forwarded from other programs such as husky on macos. ## Related Issue(s) Fixes #