BUG: Fix mixing subject hierarchy with other hierarchies

Two fixes have been applied. One is to enforce nested associations if there is a conflict of two hierarchy nodes associating to one data node.
Reminder: Nested associations prevent the scenario when two hierarchy nodes associate to the same data node, which leads to non-determinism if GetAssociatedHierarchyNode is called. In this case instead of the connections (SH --assoc--> Model <--assoc-- ModelHierarchy), this structure is created: SH --assoc--> ModelHierarchy --assoc--> Model
The other fix is to ensure reparenting to the same type of hierarchy nodes. If this proves to be too strict, then we may allow reparenting to base classes, or the alternative is to subclass the scene hierarchy model to the hierarchy types.

Also a subject hierarchy bug was fixed that occurred because the widget was created when instantiating the module (which is udesirable by itself), and this caused creation of context menu actions before external plugins had the chance to register. Now the widget is not created early, but the right connections are made at the right time.

Fixes #3911

git-svn-id: http://svn.slicer.org/Slicer4/trunk@23821 3bd1e089-480b-0410-8dfb-8563597acbee
ENH: Update CTK to ensure ctkErrorLogContext is available from python

From python, it is now possible to execute the following:

errorLogModel = slicer.app.errorLogModel()
errorLogModel.addEntry(qt.QDateTime.currentDateTime(), \
  slicer.app.applicationPid(), \
  ctk.ctkErrorLogLevel.Debug, \
  "Python", \
  ctk.ctkErrorLogContext("This is a message"), \
  "This is a message")


$ git shortlog 42700cf..0d2a634 --no-merges
Jean-Christophe Fillion-Robin (1):
      Add PythonQt decorator for ctkErrorLogContext

git-svn-id: http://svn.slicer.org/Slicer4/trunk@23822 3bd1e089-480b-0410-8dfb-8563597acbee