Feature Request: Allow profiling by process name instead of PID

I am trying to monitor memory allocation for a process that spawns other processes, all with the same executable name. The current form of `trace-bpfcc` allows me to either monitor for one PID, or for all processes (which is very slow). It would be great if all new processes of the same name would have a probe attached to them automatically.

Start by locating the trace-bpfcc entry point that selects a single PID or all processes, then read how probes are attached to processes. The feature is done when a process-name option automatically covers newly spawned processes with that executable name without monitoring unrelated processes; no specific files or tests are named.

Written by the indexing model from the issue text.