This is a very simple gitlab CI manifest to just check the tag on this
pipeline schedule it on Zombienet k8s runner and is the SA inject to the
runners in privileged enough to run command within the cluster or not

---------

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

This PR introduces the Kubernetes Provider for the SDK, with the use of
kube.rs for common operation and a custom file server using axum to
transfer files back and forth the nodes.

https://github.com/paritytech/zombienet-sdk/issues/35

This also includes the refacto of the native provider to reflect changes
to the provider structure with weak references and simplifying the use
of abstractions

---------

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

This PR lists some issues and suggested fixes for them (feel free to
pick them up separately and close this PR):

In addition to issues outlined in
https://github.com/paritytech/zombienet-sdk/issues/117#issuecomment-1867941395,
here are some issues spotted when writing
https://github.com/paritytech/disabling-e2e-tests:
- runtime genesis patch is applied incorrectly (extra `/genesis` pointer
shouldn't be added)
- malus accepts
[subcommands](https://github.com/paritytech/polkadot-sdk/blob/4c0e0e071355c1048d75fba538c96c35ac743547/polkadot/zombienet_tests/functional/0008-dispute-old-finalized.toml#L25),
having a command with spaces not supported, so I added a subcommand
support
- some types need to be exported in order to be able to reuse
setup/helper functions across multiple tests
- test cleanup doesn't always work (zombie polkadot processes - not
fixed here)

---------

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

Testing with moonbeam and found that the resulting chainspec produced
using the `moonbase-local` chain develops the following issue after the
generated plain chainspec is updated with the relevant para id:

```
Error: Zombienet(SpawnerError(Provider error
Caused by:
    File generation failed: Error: Service(Other("Error parsing spec file: trailing characters at line 25 column 14"))
```

The initial chainspec built from the binary is fine, but once
https://github.com/paritytech/zombienet-sdk/blob/e60deb25/crates/orchestrator/src/generators/chain_spec.rs#L345-L349
runs the issue occurs, as seen in the the following diff:

```
--- moonbase-local-plain copy.json	2024-02-11 02:51:15
+++ moonbase-local-plain.json	2024-02-11 02:52:24
@@ -11,7 +11,7 @@
     "tokenSymbol": "UNIT"
   },
   "relayChain": "westend-local",
-  "paraId": 1000,
+  "paraId": 2000,
   "codeSubstitutes": {},
   "genesis": {
     "runtime": {
\ No newline at end of file
@@ -22,19 +22,19 @@
         "balances": [
           [
             "0xf24ff3a9cf04c71dbc94d0b566f7a27b94566cac",
-            1208925819614629174706176
+            1.2089258196146292e24
           ],
           [
             "0x3cd0a705a2dc65e5b1e1205896baa2be8a07c6e0",
-            1208925819614629174706176
+            1.2089258196146292e24
           ],
           [
             "0x798d4ba9baf0064ec19eb4f0a1a45785ae9d6dfc",
-            1208925819614629174706176
+            1.2089258196146292e24
           ],
           [
             "0x773539d4ac0e786233d90a233654ccee26a613d9",
-            1208925819614629174706176
+            1.2089258196146292e24
           ]
         ]
       },
\ No newline at end of file
@@ -45,7 +45,7 @@
         "multiplier": "8000000000000000000"
       },
       "parachainInfo": {
-        "parachainId": 1000
+        "parachainId": 2000
       },
       "ethereumChainId": {
         "chainId": 1280
\ No newline at end of file
@@ -503,19 +503,19 @@
         "candidates": [
           [
             "0xf24ff3a9cf04c71dbc94d0b566f7a27b94566cac",
-            1000000000000000000000
+            1e21
           ],
           [
             "0x3cd0a705a2dc65e5b1e1205896baa2be8a07c6e0",
-            1000000000000000000000
+            1e21
           ]
         ],
         "delegations": [],
         "inflationConfig": {
           "expect": {
-            "min": 100000000000000000000000,
-            "ideal": 200000000000000000000000,
-            "max": 500000000000000000000000
+            "min": 1e23,
+            "ideal": 2e23,
+            "max": 5e23
           },
           "annual": {
             "min": 40000000,
\ No newline at end of file
@@ -552,7 +552,7 @@
         "eligibleCount": 50
       },
       "crowdloanRewards": {
-        "fundedAmount": 3000000000000000000000000
+        "fundedAmount": 3e24
       },
       "authorMapping": {
         "mappings": [
\ No newline at end of file
@@ -611,6 +611,11 @@
           "0xf24ff3a9cf04c71dbc94d0b566f7a27b94566cac",
           "0x3cd0a705a2dc65e5b1e1205896baa2be8a07c6e0"
         ]
+      },
+      "aura": {
+        "authorities": [
+          "5HEL3iLyDyaqmfibHXAXVzyQq4fBqLCHGMEYxZXgRAuhEKXX"
+        ]
       }
     }
   }
```

The fix appears to be to enable the
[`arbitrary_precision`](https://github.com/serde-rs/json/blob/master/Cargo.toml#L75)
feature on `serde_json`, which can be seen at
https://github.com/paritytech/polkadot-sdk/pull/2987/files. Manually
tested and solves the issue for me.

We want to add an `startupProbe` setting to the fileserver pod.

- Added basic axum fileserver to upload/download files temporary to
prevent error due to failure with exec + tar using kube.rs
- Added build and push to repository of image to be used in k8s

Add cache to workflows.

This pr make possible to add a new parachain to a running network (see
`add_para.rs` example), for that we allow to create a new parachain
config (using the same builder but in a different context) like this:

```rs
let para_config = network.para_config_builder()
        .with_id(100)
        .with_default_command("polkadot-parachain")
        .with_collator(|c| {
            c.with_name("col-100-1")
        })
        .build()?;
```
And then deploy that parachain by calling `add_parachain` (the second
parameter of the fn allow to use a custom chain-spec for the
relaychain).

```rs
network.add_parachain(&para_config, None).await?;
```

// TODO:
- [x] docs
- [ ] test (integration)

Small fix for `pjs` example.

- Add `pjs-rs` support and mimic the
[javascript](https://polkadot.js.org/apps/#/js) tab from polkadot.js
apps/
- Allow to use an external file or just an string with the `js/ts` code,

TODO: We should implement integration tests for this feature.

Changes to publish `0.1.0-alpha.0` version.

Fix parachain spec filename (local) to use when we spawn collators.
Also, adding `Context` to spawner to improve error reporting.

cc @pgherveou



---------

Co-authored-by: PG Herveou <pgherveou@gmail.com>

Adding `tracing` and replace all the `println`. We should add more info
in a followup pr.
Thx!

Call `add_collator_selection` to customize `invulnerables` for both
session and aura keys.
cc @pgherveou

Following up on take 1
https://github.com/paritytech/zombienet-sdk/pull/124

Apart from better logs, I realize that one of the only thing missing now
for us to start consuming this project is a top level package available
(with it's dependencies) on crates.io. This PR serves mainly as a
discussion point to get there.
It would be great if we could publish an early version (0.0.1?) on
crates.io so that we can start using this asap.

Register the parachains (that aren't included in the genesis) after we
run the verifier and remove the need for using sleep.
Thx!

just wanted to throw a quick implementation that exposes the
OnclineClient on the node.
This would make the sdk super useful to enable cross chain e2e tests in
ink!

---------

Co-authored-by: Javier Viola <pepoviola@gmail.com>

- Split native provider into multiple smaller files and each with their
respective tests
- Update ProviderNode.command() to ProviderNode.program()
- Update ProviderNamespace.id() to ProviderNamespace.name()