Bugzilla

- Download `libnss`, similar to how an artifact build does it
- Setup Rust/Cargo to link to the `libss`, maybe using the `NSS_STATIC` and `NSS_DIR` env vars like we do in app-services.

Implementing this is an alternative to https://bugzilla.mozilla.org/show_bug.cgi?id=1958000, if we can make Cargo do the linking then we don't need to do anything special with `mach rusttests`.

Once https://bugzilla.mozilla.org/show_bug.cgi?id=1980203 is merged, then we should be able to run `cargo test -p` to test our app-services crates.  However, one additional issue is linking to NSS.

We should create a mach comm

- Download `libnss`, similar to how an artifact build does it
- Setup Rust/Cargo to link to the `libss`, maybe using the `NSS_STATIC` and `NSS_DIR` env vars like we do in app-services.

Implementing this is an alternative to https://bugzilla.mozilla.org/show_bug.cgi?id=1958000, if we can make Cargo do the linking then we don't need to do anything special with `mach rusttests`.

Once https://bugzilla.mozilla.org/show_bug.cgi?id=1980203 is merged, then we should be able to run `cargo test -p` to test our app-services crates.  However, for many of our crates, we still need to figure out how to link to NSS.

Let's create a mach command that sets up the app-services environment, similar to `verify-desktop-environment.sh`.  It should:

- Run `./mach build` to build NSS
- Set the `NSS_DIR` variable to point to the the built NSS in the object directory

I don't think it needs to do anything else at this point, but we may want to extend it to do more in the future.

Implementing this is an alternative to https://bugzilla.mozilla.org/show_bug.cgi?id=1958000, if we can make Cargo do the linking then we don't need to do anything special with `mach rusttests`.