Distant scenarios and key=value configuration

[pandatix]

Currently, scenarios are provided as zip archives. This is sufficient, but we observed multiple usages of the same scenario with constants redefined.

For instance, during the NoBrackets 2024 we used 13 kubernetes.ExposedMonopod for the SDK, and in the main.go file we only changed the private registry, Docker image name and connection info... To compile it thus become 50 Mo, and at scale 650 Mo for a small CTF.

This highlighted the need to configure a generic ExposedMonopod binary, with a key=value mecanism.

The idea to implement could be to permit a challenge to use a distant scenario, put it in a cache (locally ?), and pass key=value pairs to the state on deployment. This could further enhance current capabilities, with the possibility to pass, for instance, a VLAN id for network segregation.