build: configured docker build pipelines for cargo native addons

- Switched Docker images to build native addons via cargo/napi-rs (`OMP_NATIVE_BUILD_BACKEND=cargo`) instead of Bazel.
- Updated Cargo.toml workspace members explicitly to prevent loading errors from stale directories under crates/.
- Added depth-agnostic patterns to .dockerignore files to exclude nested build outputs from Docker build contexts.
- Added OMP_NATIVE_CARGO_PROFILE environment variable to support configuring cargo profiles for addon builds.

Cargo.toml

@@ -1,5 +1,18 @@
 [workspace]
-members = ["crates/pi-*", "crates/vendor/*"]
+# Explicit, not `crates/pi-*`: a glob member that resolves to a directory
+# without a Cargo.toml (a deleted crate whose dir survives `git reset --hard`
+# because an ignored file stayed behind) is a hard error that fails the whole
+# workspace, not a skipped entry.
+members = [
+   "crates/pi-ast",
+   "crates/pi-builtins",
+   "crates/pi-iso",
+   "crates/pi-natives",
+   "crates/pi-shell",
+   "crates/pi-voice",
+   "crates/pi-walker",
+   "crates/vendor/brush-core",
+]
 resolver = "3"
 
 [workspace.package]