ci: defer ban_raw_subprocess dylint to follow-up issue

Per CR feedback on PR #262 the dylint needs zccache's
build_dylint_driver.py infrastructure (published dylint_driver 5.0.0
doesn't build against nightly-2026-03-26) plus a tightened scope
filter and qpath handling. That's enough scope to warrant its own PR.

Strip the dylint crate, the workspace metadata + exclude entries,
and the CI step. Keep the user-facing LTO fix (the actual bug from
issue #261).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: zackees

.github/workflows/check-ubuntu.yml

@@ -33,14 +33,5 @@ jobs:
         run: soldr cargo clippy --workspace --all-targets -- -D warnings
       - name: Lint subprocess spawns
         run: uv run python ci/find_direct_subprocess.py --fail
-      # Custom dylint enforces the rule that all subprocess spawns go
-      # through the wrappers in `fbuild_core::{subprocess,containment}`.
-      # See `dylints/ban_raw_subprocess/`. The dylint crate has its
-      # own nightly toolchain (rust-toolchain.toml inside the dir);
-      # `cargo dylint` picks it up automatically.
-      - name: Install cargo-dylint
-        run: cargo install cargo-dylint dylint-link --locked
-      - name: Run ban_raw_subprocess dylint
-        run: cargo dylint --all -- --workspace --all-targets
       - name: Test
         run: soldr cargo test --workspace

Cargo.toml

@@ -16,14 +16,6 @@ members = [
     "crates/fbuild-library-select",
     "bench/fastled-examples",
 ]
-exclude = [
-    # Dylint lints live in their own nightly toolchain — see each
-    # dylint's rust-toolchain.toml. Not part of the workspace build.
-    "dylints/ban_raw_subprocess",
-]
-
-[workspace.metadata.dylint]
-libraries = [{ path = "dylints/*" }]
 
 [workspace.package]
 version = "2.2.4"