Ensure graceful shutdown by removing log.Fatal and panic calls

[rogercoll]

The tracer/monitorPIDEventsMap function does not propagate any error to its parent function, instead it fails with a fatal error: https://github.com/open-telemetry/opentelemetry-ebpf-profiler/blob/v0.0.202540/tracer/tracer.go#L767

Given that the function runs periodically, the error could be logged instead of exiting the program.

[christos68k]

There's more usage of log.Fatal and panic that we should equally address as the profiler is going to be running inside OTel Collector. Should we rename this issue?