Switch to testcontainers

[stormshield-gt]

Fixes #80

This PR migrates the whole test suite to testcontainers.

This notably removes dependencies against the unmaintained dockertest and dockertest-server. This will unlock #68 and other developments that were blocked by upstream issues. Notably we can now bump the tested Vault version.

To be able to run tests in parallel and factorize the test setup logic, I've introduced a new crate vaultrs-tests and update the CI accordingly.
The CI workflow now go from 9m 18s to 4m 23s. The local test duration is also greatly reduced.

Note: I've also updated the rust edition that uses the new cargo resolver, implying that we now use the cargo resolver v2 with feature unification. Because of this, reqwest will choose native-tls over rustls if both features are activated. I use use_rustls_tls() in that case to override this behavior to force rustls. This matches the old behavior and I think it makes more sense.

Note: I tried to strictly port the test doing the less refactoring possible to ease the review. I plan to do a followup PR, to further cleanup the test suite.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	Generic Password	2777cb9	vaultrs-tests/tests/api_tests/userpass.rs	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[stormshield-gt]

The git guardian warning is because I introduced hard-coded private keys to ease the test setup.
I do not consider this as bad practice because the secrets are not sensitive. This is widely used by well-known crates as rustls.
However, if we can't add an exception to the git guardian check, I will consider generating the certificate on the flight with rcgen.

[stormshield-gt]

If fixed the GitGuardian issue, @Haennetz do you know when you will have some bandwidth to review this?

[Haennetz]

If fixed the GitGuardian issue, @Haennetz do you know when you will have some bandwidth to review this?

I hope that i can review it on Wednesday

[Haennetz]

Wednesday

I need some additional time to review it I will finish the review on Friday. Looks really good so fare. Nice work 👍

[stormshield-gt]

Thanks for taking a look!

[Haennetz]

@stormshield-gt Really nice work, I only have 3 questions, that are only out of curiosity. I will approve it already. You should be able to merge it by your self.

[stormshield-gt]

Thanks again for your review @Haennetz, I will merge this now