fix: gate the min dirs Mesh enrolment row behind the remote-access feature - #1150

_{Comment @coderabbitai help to get the list of available commands.}

Reviewed — correct, and I verified the path CI cannot reach

The gating is symmetric and complete: the import, both DirsLookup fields, the MeshGroup enum and its impl, the mesh_row closure, both use sites (the Config and State branches), and the test fixture are all behind #[cfg(feature = "remote-access")]. No dangling reference on either side.

The part worth flagging: remote-access is off by default (crates/minimal/Cargo.toml: "Off by default: gates the mesh and ssh-forward CLI subcommands"), and no workflow passes --features remote-access. So green CI here only proves the feature-off build compiles — which is the easy half, since that is the half where the code is removed. The newly gated code is the side nothing builds.

I compiled it locally to close that gap:

cargo check -p minimal --features remote-access
Finished `dev` profile [unoptimized + debuginfo] target(s) in 28.65s

Clean — no errors, no new warnings in minimal (the sandbox2 warnings are pre-existing and unrelated).

This is a general property of the repo rather than a problem with this PR: any future change to feature-gated code lands unverified by machine. Worth a cargo check --features remote-access step in CI if this gating pattern spreads — cheap, since it is a check rather than a build.

The fix itself is right for gominimal/inbox#390: the row advertised a path for a command this build does not ship, and gating it at the same feature that gates the command keeps the two from drifting apart again.