test(unit): don't generate test reports for quicker tests

[lahabana]

This uses go test instead of ginkgo cli This seems to run tests twice as quick.

Checklist prior to review

• Link to relevant issue as well as docs and UI issues --
• This will not break child repos: it doesn't hardcode values (.e.g "kumahq" as a image registry) and it will work on Windows, system specific functions like syscall.Mkfifo have equivalent implementation on the other OS --
• Tests (Unit test, E2E tests, manual test on universal and k8s) --
  • Don't forget ci/ labels to run additional/fewer tests
• Do you need to update UPGRADE.md? --
• Does it need to be backported according to the backporting policy? (this GH action will add "backport" label based on these file globs, if you want to prevent it from adding the "backport" label use no-backport-autolabel label) --

[michaelbeaumont]

Sort of odd that it takes so much longer, assuming it's running the same tests but 🤷

[lahabana]

It's because of the way ginkgo runs stuff in parallel: https://onsi.github.io/ginkgo/#mental-model-how-ginkgo-runs-parallel-specs

It makes a lot of sense for e2e tests (which are long). It makes less sense for many small unit test suites.