Mechanism to exclude methods from tracing

[LinqLover]

Some expressions/processes have a large computational foot stamp because they execute expensive methods such as ClassDescription>>#packageInfo that, at the same time, do not include any relevant side effects to the debugged system. As a "last resort" optimization performed by the user of the tool, it might be helpful to declare an exclusion list of methods that should be ignored during tracing. The tracer would be responsible for running all invocations of these methods outside of the simulator. See LinqLover/SimulationStudio#54.

Discuss a proper UI:

• analogously to filters, select a context to exclude it by example
• would benefit from Robust user interrupts during stepping #64
• Challenging: Exclude method but not block called by function