Test strategy for our providers on the CI about parsec

[hug-dev]

We could add an optional argument when launching Parsec to specify a configuration file path and use this one. That way we can have in-tree one configuration file per provider and test them independently 😄

And one more with all of them 😈

[hug-dev]

We would have the following test structure (in tests):

all.sh -> Executing all of the tests below + rustfmt + clippy (will work only if everything is installed)
per_provider/ -> Test executed only with a single provider
    normal/
    stress/
    fuzz/
    persistence/
    PROVIDER_NAME/ -> Folder containing the Dockerfile and config.toml file per provider
        Dockerfile
        config.toml
all_providers/ -> Tests using all providers
    Dockerfile -> Would contain all providers (not published)
    config.toml
    mod.rs
cross_compilation/ -> Testing cross compilation of Parsec
    Dockerfile
    Cross.toml

The following Dockerfile would be needed:

1. one for the TPM provider + tss-esapi crate (there is one in parallaxsecond/rust-tss-esapi repo already)
2. one for the PKCS 11 provider
3. one for the Mbed Crypto provider + crate (cf #62)
4. one combining 1, 2 and 3 for the all_providers tests
5. one for cross-compilation, that already exists

Exactly the same tests (except cross_compilation) could be done on an Arm platform, on the CI, check #55 to also have coverage for Arm.