chore: vendor nucleo-ext + fork, so we can depend on our changes properly (#3284)

We cannot publish to crates.io without specifying a version, and we
cannot do that without properly forking nucleo. We're shipping
atuin-nucleo, but will likely drop this if we can get our changes
upstream. This is highlighted in the README + manifest, and the original
author is still included.

Originally forked here: https://github.com/atuinsh/nucleo-ext

cc @BinaryMuse - this should just be a vendor + restructure, but would
appreciate the sanity check

## Checks
- [ ] I am happy for maintainers to push small adjustments to this PR,
to speed up the review cycle
- [ ] I have checked that there are no existing pull requests for the
same thing

1 files changed, 4 insertions, 2 deletions

diff --git a/Cargo.toml b/Cargo.toml
index 0f4203b0..65bfd48d 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -1,8 +1,8 @@
 [workspace]
-members = ["crates/*"]
+members = ["crates/*", "crates/atuin-nucleo/matcher", "crates/atuin-nucleo/bench"]
 
 resolver = "2"
-exclude = ["ui/backend"]
+exclude = ["ui/backend", "crates/atuin-nucleo/matcher/fuzz"]
 
 [workspace.package]
 version = "18.13.2"
@@ -26,6 +26,8 @@ atuin-server = { path = "crates/atuin-server", version = "18.13.2" }
 atuin-server-database = { path = "crates/atuin-server-database", version = "18.13.2" }
 atuin-server-postgres = { path = "crates/atuin-server-postgres", version = "18.13.2" }
 atuin-server-sqlite = { path = "crates/atuin-server-sqlite", version = "18.13.2" }
+atuin-nucleo = { path = "crates/atuin-nucleo", version = "0.6.0" }
+atuin-nucleo-matcher = { path = "crates/atuin-nucleo/matcher", version = "0.3.1" }
 base64 = "0.22"
 crossterm = "0.29.0"
 log = "0.4"