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>

Don't try and run the tests that require njs if it isn't enabled.

Closes: https://github.com/nginx/unit/issues/1411
Fixes: 43c4bfdcd ("tests: "if" option in http route match")
Signed-off-by: Andrew Clayton <a.clayton@nginx.com>

[ Tweaked subject - Andrew ]
Signed-off-by: Andrew Clayton <a.clayton@nginx.com>

Rename this to 'test_wasm-wasi-component.py' to match the language
module name and the name as used in the CI.

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>

We can now get list objects from the /status endpoint in the case of
having different versions of the same language module.

That led to this error

  >       return d1 - d2
  E       TypeError: unsupported operand type(s) for -: 'list' and 'list'

We already cover a similar case for when we have simple strings so add
this to that.

Signed-off-by: Andrew Clayton <a.clayton@nginx.com>

Now that the `/status` endpoint returns a list of loaded language
modules, e.g

  {
      "modules": {
          "python": {
              "version": "3.12.2",
              "lib": "/opt/unit/modules/python.unit.so"
          },

	  ...
      ...
  }

This broke 'test/test_status.py' in a number of ways

  1) The check for all the object values being 0 at startup is no longer
     true with the modules section.

  2) The find_diffs() check broke trying to subtract strings from
     strings.

So don't include the 'modules' section in the check_zeros() check and in
the find_diffs() check, if we're dealing with strings do a basic
compare returning that value instead.

[ Commit message - Andrew ]
Co-developed-by: Andrew Clayton <a.clayton@nginx.com>
Signed-off-by: Andrew Clayton <a.clayton@nginx.com>

Add the following tests cases:

1. When "factory" key is used inside the "targets" option.
2. When "factory" key is used at the root level of python application
   config.
3. When factory returns invalid callable or When factory is invalid
   callable

Link: <https://github.com/nginx/unit/pull/1336>
[ Commit subject & message formatting tweaks - Andrew ]
Signed-off-by: Andrew Clayton <a.clayton@nginx.com>