Creating CLI e2e tests

[danielbdias]

This PR adds a PoC for CLI e2e tests on Tracetest.

To run these tests locally, you can run the following commands:

cd testing/cli-e2etest
make test

Or, if you want to run with your local compilation:

make build-docker
rm -rf dist
make build-go

export TRACETEST_COMMAND=$PWD/dist/tracetest
export TEST_ENVIRONMENT=jaeger
export TAG=latest

cd testing/cli-e2etest
make test

Loom: https://www.loom.com/share/92fe592a94614b57a85fd0715f1c9293

Changes

• Added CLI e2e action on Github Actions
• Added test code for DataStores, version and help commands

Fixes

• Found a wrong behavior with apply command, that was not considering yaml when parsing a datastore

Checklist

• tested locally
• added new dependencies
• updated the docs
• added a test

[mathnogueira]

Is that correct? We expect the same value for Content-Type and Accept? Doesn't this go against the PR Sebastian opened to support different content types for inputs and outputs of the API?

[danielbdias]

No, because with that we are saying "we expect the same input and output contentType from the API", on future versions we have the idea of sending yaml and handling the output with the --output-format flag that the user uses.

[schoren]

for future referece, if you don't need different request and response content types, you can pass just one (either) header and everything falls back to that

[danielbdias]

Cool! I will revisit this decision and start using different Content-Type and Accept after we visit the PR #2523 .
In the future, the main idea is that the backend should be responsible for formatting entities to avoid replication of the same logic and both CLI and Backend.