Fix PRename::whyEvent to better handle renaming

If something is renamed to the event requested, whyEvent will now notice
this and present a list of possible events that the component may offer
to make the whole process offer it.
Stops prettyPrint output from being used as input

Now the actual underlying process is used when probe/inspect is chosen
from the context menu, which is a more robust method and doesn't rely on
the prettyPrint output being unambiguous. This involves the inclusion of
a new base class ProcessItem from which TransitionItem and InspectItem
derive; a good thing to have anyway to avoid code duplication.
Event sets in tool tips are now shortened if possible

Adds a haskell function to monadically prettyPrint lists of events, and
calls it from PBase::displayEventList().
Rework of event query system

- Event query will now use context: each entry in the model gets a
  different set of events to work with, rather than just one event
  queried for all nodes. This means that the input query is always
  relevant only to the root node in the inspector (which is probably
  what was wanted).
- Fixes the renaming operator to support one-to-many renaming.
- Adds support for translation into other languages.
- Adds the ability to display a list of events in various formats.