make integration tests more robust

[geyslan]

chore: make integration tests more robust

- Add generic functions to check received events in different manners:
  - ExpectAllInOrder
  - ExpectAllEqualTo
  - ExpectAtLeastOneOfEach
  - ExpectAnyOfEach
- Add waitForTraceeOutputEvents function to wait for tracee output
  events until buffer fills with certain number of events or
  timeout occurs.
- Add waitforTraceeStop function to wait for tracee to stop or until
  timeout occurs.
- Remove tester.sh concentrating all event filter tests in
  event_filters_test.go.
- Create syscaller tool to easily generate syscalls from the command
  line (strictly for integration tests). It reuses the tracee events
  package.
- Fix goroutine leaks, deadlocks and race conditions.

Fixes: #2681

Initial Checklist

• There is an issue describing the need for this PR.

Type of change

• Code refactor (code improvement and/or code removal)

How Has This Been Tested?

make test-unit
sudo make test-integration

[josedonizetti]

I want to review this one

[rafaeldtinoco]

TODO: We should merge this one at the end of the milestone (no matter if its on the bug fix window) just so we don't change tests while doing the release. @josedonizetti I'll let you take care of it (as you've requested to review and since we've spoken offline about it). Cheers!

[rafaeldtinoco]

@geyslan shouldn't integration tests binary be inside ./dist/ like all other binaries (including tracee-gpt, for example). Its a convention, I wonder if we could make the same for this binary.

[geyslan]

@geyslan shouldn't integration tests binary be inside ./dist/ like all other binaries (including tracee-gpt, for example). Its a convention, I wonder if we could make the same for this binary.

Currently the syscaller is used only for the golang integration tests that lie under ./tests/integration/syscaller. But if you have plans to run it from other scripts and so, I think the move makes sense.

[josedonizetti]

@geyslan shouldn't integration tests binary be inside ./dist/ like all other binaries (including tracee-gpt, for example). Its a convention, I wonder if we could make the same for this binary.

Currently the syscaller is used only for the golang integration tests that lie under ./tests/integration/syscaller. But if you have plans to run it from other scripts and so, I think the move makes sense.

+1, also think that if are not using it elsewhere, as it was created specifically for e2e, we should have it under ./tests/integrations

[rafaeldtinoco]

+1, also think that if are not using it elsewhere, as it was created specifically for e2e, we should have it under ./tests/integrations

Problem with that is now we are not "out-of-tree" building environment just because of this binary. We have just spread leftovers and artifacts to internal directories in the source tree directory (which is not what we should do IMO).

Every time a new binary is created, we have to ignore that binary (if its dir is not already ignored). Every time we clean things, we need to clean the generated binary instead of the out-of-tree directory (dist).