Integration test: Repeating test suites with different containerized environments

[mariomac]

The aim of this PR is being able to run the integration tests both in services that embed debug info and services that don't. But it will be also useful to test the auto-instrumenter when, instead of the executable name, we specify the port name.

Now the docker-compose environment can be configured via environment. And instead of spinning it up/down from the Makefile, we do it from the Go tests.

The normal "Tests" will be now run as subtests of higher-level suites. Each suite will:

• Spinup the Docker cluster and optionally override the configuration.
• Run the subtests
• Destroy the Docker cluster

Now we have two suites:

1. the baseline suite that just runs the HTTP RED metrics test with the default values
2. a suite that forces the instrumented service to be built without debug information, and then run again the HTTP RED metrics test.

[codecov-commenter]

Codecov Report

Merging #45 (6162c9d) into main (81d7cf7) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #45   +/-   ##
=======================================
  Coverage   50.30%   50.30%           
=======================================
  Files          14       14           
  Lines         833      833           
=======================================
  Hits          419      419           
  Misses        378      378           
  Partials       36       36           

Flag	Coverage Δ
unittests	50.30% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[grcevski]

LGTM! This is awesome, I can't wait to try it. I am thinking I can now use this for the gRPC integration tests, as well as maybe adding an HTTPS service test.