[uss_qualifier] Add datastore unit tests

[the-glu]

Add datastore unit tests to ensure various DatastoreDBNode works against real database.

Database are spawn using testcontainer, I added DiD support to start thoses containers.

I fixed is_reachable for yugabyte that require hashed password in some cases.

I used a custom image that I build for cockroachdb with tls 1.1 support, I didn't find old images (2017..). I suppose we want to upload that on the official interuss account?

[mickmis]

That's really great, thanks!

I used a custom image that I build for cockroachdb with tls 1.1 support, I didn't find old images (2017..). I suppose we want to upload that on the official interuss account?

Indeed. And actually I'd go as far as uploading all images used in this test in the interuss Docker Hub repo. WDYT @BenjaminPelletier ? We would need you to do so :)

But that should not prevent this PR from going in IMO.

[mickmis]

Does this prevent the project from being run on some OSs? Or is it transparent whether we are on Linux, MacOS or Windows?

[mickmis]

In addition, shouldn't this be added as a dev dependency to avoid users having to depend on this?
(or maybe it is already the case and I did not notice it)

[the-glu]

Yes, that a dev dependency, I added in the wrong group ^^'

For OS that should be transparent*, and in all cases unit tests run in a controller environment in a docker container by default, so that shouldn't interfere :)

• As long as we can start docker containers ^^'

[the-glu]

Since we don't have a dev group yet, but there are other things that should go into that 'group', I suggest we postpone the fix in a future PR, with two separate groups and two image, one for 'tooling' and a light one with only running dependencies installed :)

[mickmis]

@the-glu SGTM, if you don't do it in the short-term, could you open an issue about it?

[BenjaminPelletier]

I used a custom image that I build for cockroachdb with tls 1.1 support, I didn't find old images (2017..). I suppose we want to upload that on the official interuss account?

Indeed. And actually I'd go as far as uploading all images used in this test in the interuss Docker Hub repo. WDYT @BenjaminPelletier ? We would need you to do so :)

interuss/insecurecockroach should now be available (mirrored from mcuoorb). If we use this image, then I think :latest is fine since we control updates. But for any external image, I would expect us to pin to a specific version to avoid unexpected breakages when the remote changes.

I would expect us to follow whatever we document for users for the other images. We could consider mirroring images of the specifically-supported underlying database technologies via the interuss Docker org, but that would be a separate discussion. Until we decide otherwise, I think our standard procedure has our users use the original images so we should use those also.

[mickmis]

FTR: #1094 has been merged while it contained the commits present in this PR. This PR now contains only the fixes that happened in between: change in uv.lock and use of interuss docker hub repo.