Added:
  - Helper to perform a runtime upgrade on the relaychain
 
```rust
    let wasm = "file_path__or__url_to_*.compact.compressed.wasm";
    network
        .relaychain()
        .runtime_upgrade(RuntimeUpgradeOptions::new(wasm.into()))
        .await?;
```

- Fix stash derivation (use `//`)
- Add `evm` support, you can set your parachain as evm based with
`evm_based(choice: bool)`.


Fix: #247 
cc: @AlexD10S / @al3mart

This is nothing big  :) 

The code execution logic is already present under `pjs` function, yet it
is duplicated for `pjs_file` function.

This change re-uses the existing code, so that you won't have to change
it twice in the future.

Co-authored-by: Javier Viola <363911+pepoviola@users.noreply.github.com>

Fixes:
- `wait` methods for metrics
- `path` checking for `native` provider validation.

- Add binaries verification to
`validate_spec_with_provider_capabilities`
- Improve error display in providers.

When testing `zombienet-sdk` with cross-chain calls with Asset Hub, we
found that the hrmp channels passed to the chainspec caused the
following issue:

`Error: "Invalid JSON blob: invalid type: map, expected a tuple of size
4 at line 1 column 2794"`

This is because the values of `HrmpChannelConfig` serialise to a map
instead of a tuple, as expected by
https://github.com/paritytech/polkadot-sdk/blob/fc906d5d0fb7796ef54ba670101cf37b0aad6794/polkadot/runtime/parachains/src/hrmp.rs#L492.
Tests were updated accordingly to facilitate this fix.

Additional commits were also added to enable some of Asset Hub on
Polkadot functionality observed in the classic Zombienet repo, so that
we are able to launch a local Polkadot network with Asset Hub should
anyone require. Example configuration files can be found at the bottom
of https://github.com/r0gue-io/pop-cli/pull/278/files for anyone
interested, although that PR is still a work in progress and dependent
on this one being accepted.

PS - I added tests where I could, but additional tests might require
some minor refactoring to make it easier to test only the logic that is
changed by this PR, which I am not sure what the appetite is? An example
would be refactoring the file name generation in `keystore.rs` into its
own function to more easily test the outputs without the `scoped_fs`.

WIP

---------

Co-authored-by: Javier Viola <363911+pepoviola@users.noreply.github.com>

Add: 
 - Bump subxt version
 - Change visibility for internal crates

Change exports.

@rzadp @Bullrich

This pr introduce the ability to set the `base_dir` used by the
`namespace`. This allow users to reuse the same node's directories
(config and database) and re-start the network from the latest state in
sequential runs.

Thx!

fix #218

cc @sandreim thanks for the suggestion :)

Firstly, thank you for an amazing library! The original zombienet is a
Polkadot staple and now being able to use it completely from Rust is a
game changer for us: as you may be aware, we have integrated
zombienet-sdk with
[pop-cli](https://github.com/paritytech/zombienet-sdk).

In doing so, we needed to add a few getters to the public api to be able
to present certain information to the user, as well we expose a little
more of the inner errors. This PR simply upstreams these changes.

It also includes two additional fixes, which may be better implemented
based on your guidance:
- collator args werent working for us when specified in a config file,
which seemed to be due to missing `--` in the args list provided by
calling functions.
- artifact path wasnt set when trying to build a chain spec. This may no
longer be required based on the changes in
https://github.com/paritytech/zombienet-sdk/commit/c7ce50c0

I am happy to add tests if you are open to these changes. 

Couple of fixes for docker provider and to use an external tool to build
the chain-spec.

docker support 

---------

Co-authored-by: Javier Viola <javier@parity.io>

Add:
 - logs methods in NetworkNode

- [k8s] fix `cmd` generator for collators (needs to use exposed ports).

based on #190 

cc: @s0me0ne-unkn0wn

Fix https://github.com/paritytech/zombienet-sdk/issues/169

- Add logic to retrieve available args from node before spawning the
full network using the output of the command with --help

Concatenating the command line option and its value doesn't really work.
The shell treats `--opt val` as a single argument `--opt val` instead of
`--opt` `val` and fails to execute. This PR fixes that by separating
options from their values.

Error example:
```
error: unexpected argument '--workers-path ~/.cargo/bin/workers-1.6' found

  tip: a similar argument exists: '--workers-path'
```

Co-authored-by: Javier Viola <363911+pepoviola@users.noreply.github.com>

Add: 
  - async drop impl in k8s namespace / `noop` in native.
  - Modify example test.

Add:
 - Logic to use db_snapshot in both native/k8s providers
 - Small fix on chain_spec_path (for both native/k8s)
 - New example `db_snapshot`

Add small validation, mostly to ensure that the `image` is set in k8s.

fix #143

Fix #173 

We should also add a follow up issue to improve the docs.

cc: @s0me0ne-unkn0wn