Simplify clear implementation

[nibon7]

Description

This PR uses the crossterm api to reimplement clear command, since crossterm is cross-platform.
This seems to work on linux and windows.

User-Facing Changes

N/A

Tests + Formatting

• cargo fmt --all -- --check to check standard code formatting (cargo fmt --all applies these changes)
• cargo clippy --workspace -- -D warnings -D clippy::unwrap_used to check that you're using the standard code style
• cargo test --workspace to check that all tests pass (on Windows make sure to enable developer mode)
• cargo run -- -c "use std testing; testing run-tests --path crates/nu-std" to run the tests for the standard library

After Submitting

N/A

[fdncred]

I have a couple ideas and concerns here. Generally, I like the simplification and hope we can use it. Thanks!

1. crossterms's ClearCommand calls ansi escape sequences. I wonder if that's a big deal since I assume there are terminals that don't handle ansi escape sequences. We support those terminals now by turning off ansi escape sequences via config. Windows has a special directive, seen below. I wonder if crossterm has a function that checks if the terminal supports ansi escape sequences? If so, we could have a check to see and then clear the old way maybe?
2. It may be a good idea to implement switches for what crossterm provides as parameters when not on windows. Not sure if that's a good idea or not. FYI - all of these ansi escape sequences are already in nushell in the ansi --list command.

    fn write_ansi(&self, f: &mut impl fmt::Write) -> fmt::Result {
        f.write_str(match self.0 {
            ClearType::All => csi!("2J"),
            ClearType::Purge => csi!("3J"),
            ClearType::FromCursorDown => csi!("J"),
            ClearType::FromCursorUp => csi!("1J"),
            ClearType::CurrentLine => csi!("2K"),
            ClearType::UntilNewLine => csi!("K"),
        })
    }

    #[cfg(windows)]
    fn execute_winapi(&self) -> io::Result<()> {
        sys::clear(self.0)
    }

Thoughts?

[nibon7]

Nushell is built up on reedline which uses the Clear command to implement some functions, such as Painer::repaint_buffer, Painter::print_menu and Painter:clear_scrollback. So I assume the Clear command is ok.

https://github.com/nushell/reedline/blob/ff5fdb0e108186ebc6bb3c731f6c4d2908640d02/src/painting/painter.rs#L165-L167

https://github.com/nushell/reedline/blob/ff5fdb0e108186ebc6bb3c731f6c4d2908640d02/src/painting/painter.rs#L241-L244

https://github.com/nushell/reedline/blob/ff5fdb0e108186ebc6bb3c731f6c4d2908640d02/src/painting/painter.rs#L462-L466

[fdncred]

I'm willing to give this a try and we can add more switches in the future.