Suppress the output from cargo-component when we first run it to check
if it's available, otherwise you may see the following

  $ pytest test/test_wasm-wasi-component.py
  which: no go in (/home/andrew/.local/bin:/home/andrew/bin:/usr/share/Modules/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin)
  error: no such command: `component`

  	View all installed commands with `cargo --list`
  	Find a package to install `component` with `cargo search cargo-component

Note: This didn't stop the tests from working, just an aesthetic issue.

Closes: https://github.com/nginx/unit/issues/1410
Signed-off-by: Andrew Clayton <a.clayton@nginx.com>

Changes are afoot... wasm32-wasi has been renamed wasm32-wasip1, there
is also a wasm32-wasip2 (seems not yet fully realised) and wasm32-wasi
is being kept clear for an eventual WASI 1.0 release.

cargo-component targets wasm32-wasip1 by default and adapts the module
to the preview2 version of WASI supported by the component model.

This means that the component is now found under
target/wasm32-wasip1/...

Link: <https://doc.rust-lang.org/nightly/rustc/platform-support/wasm32-wasip1.html>
Link: <https://github.com/bytecodealliance/cargo-component/blob/main/README.md#wasi-support>
Signed-off-by: Andrew Clayton <a.clayton@nginx.com>