Task names and PID mapping

Created by: derkling

The current identification of task names and mapping of names to PID is rather simplistic since it assumes that a task changes its name at most one time after being created. Thus, we assume the name for a give PID is the very last comm value we get from a sched_switch event.

Reality is that a given task can change its name multiple times or that the same PID can be re-used for different tasks.

A better solution would be to consider sched_wakeup_new events to identify when a new task is created and to ensure the correct name is assigned to each PID. In case more than two names are used for the same task we should also warn the user at the very least.

Other details have been discussed in #880