🚀 [Feature]: Adopt testcontainers-go for all the storage layers

[mdelapenya]

Feature Description

After #1506, let'd adopt testcontainers-go for integration testing of the storage layers.

For those technologies having a tc-go module (see https://testcontainers.com/modules/?language=go), let's use the module; for the rest, let's use the GenericContainer approach.

PRs to raise

• arangodb
• azureblob
• badger
• bbolt
• clickhouse feat: use testcontainers-go for clickhouse tests #1506
• cloudflarekv
• coherence
• couchbase chore: use testcontainers-go for couchbase and minio #1508
• dynamodb
• etcd
• memcache
• memory
• minio chore: use testcontainers-go for couchbase and minio #1508
• mockstorage
• mongodb chore: adopt testcontainers-go for Postgres, MySQL and MongoDB #1515
• mssql
• mysql chore: adopt testcontainers-go for Postgres, MySQL and MongoDB #1515
• nats
• pebble
• postgres chore: adopt testcontainers-go for Postgres, MySQL and MongoDB #1515
• redis
• ristretto
• rueidis
• s3
• scylladb
• sqlite3

Checklist:

• I agree to follow Fiber's Code of Conduct.
• I have checked for existing issues that describe my suggestion prior to opening this one.
• I understand that improperly formatted feature requests may be closed without explanation.

[the-real-i9]

Hi @mdelapenya @gaby 🙇‍♂️. Can I submit a PR?

I've submitted a PR for Neo4j storage driver, which uses testcontainers-go, that's near approval.

Any further necessary steps after integrating the feature? I'm thinking I'll need to remove the docker run step for the target storage driver in the benchmark.yml workflow.