chore(tests): Update test files to work with Docker Compose v2

[deadlycoconuts]

What this PR does / why we need it:
It seems like v1 of Docker Compose has just been removed from all ubuntu GitHub runners as of the 29th of July (and has been ongoing since that day). This has broken the CICD pipelines of lots of repos (just take a look at the number of times that issue has been referenced), including XP. As such we can no longer run commands like docker-compose in the GitHub runners anymore and need to start updating them to use the v2 commands (to docker compose for this particular example).

For XP in particular, what broke were the Treatment Service integration tests, where we were using the testcontainers package to spin up Kafka. This version however, is also similarly super old, and calls docker-compose (v1) to spin containers in Go code. As such, this PR updates the version of testcontainers (which also requires some additional changes to the methods we need to call) so that the Docker Compose v2 commands are used instead.

Summary of Changes:

• Renaming of docker-compose to docker compose
• Bumping of testcontainers version
• Bumping of Go version (I didn't want this but we need to bump to the later/latest version of testcontainers)
• Bumping of the Go linter versions (in order to work with the newer Go version)
• Bumping of all other random dependencies after running go mod tidy in all places
• Replacement of the deprecated io/ioutil package methods with io methods (this mostly applied to the autogenerated code in clients/management/managementclient.go and clients/treatment/treatmentclient.go; I could've regenerated the code with a newer version of the code generator but I just decided to use my IDE to replace them)
• Refactoring of the integration test setup script in treatment-service/integration-test/fetch_treatment_it_test.go to use the new Docker Compose v2 commands
• Change to the existing unit test in treatment-service/models/storage_test.go to ensure that an existing unit test no longer breaks because it's performing a check on a randomly generated ID

Which issue(s) this PR fixes:

Fixes #

[tiopramayudi]

Add some comments, the rest is LGTM! Thanks @deadlycoconuts