Check before release

[yanivagman]

To avoid broken releases, we should make a list of things to check before releasing a new version of Tracee.
For now, some of these checks will have to be done manually, but eventually, we should automate it all.

Here are a few things I have in mind:

1. Make sure that libbpfgo module is up to date
2. Make sure that the tracee-ebpf/external module used by tracee-rules is up to date
3. Check that there are no verifier issues when choosing all events in tracee-ebpf (using --trace e=*)
4. Do (3) for different kernel versions, including old kernels (e.g. 4.18/4.19) and new ones (5.10+)
5. Check both CO-RE and non CO-RE builds
6. Sanity checks for different "special" features:
   a. capture artifacts (files, memory, net, etc) works
   b. table/json/gob printers output makes sense
   c. try running tracee-ebpf with some filters and validate they work as expected
7. Build documentation site (if docs site is not being built #704 haven't been fixed yet)
8. Check that the docker images (both "latest" and "slim") build correctly and run as expected

Any additions to this list are welcome