In multi-clients mode, the master client can enable or disable the further
connections from the collaboration panel. Default is "enable".
With option --disable-further-connections, initial state is "disable".

The master client can change the connect-id of the server.

Connected clients are not disconnected when mode or connect-id is changed
in the server.

This commit was generated automatically by running:

Utilities/Scripts/clang-format.bash --tracked

Change-Id: I956c730dc7c9ee4b45e61cd16959210fb0d26d0d

The vtkstd forwarding headers are deprecated, move to using the STL
headers directly.

Change-Id: I18b275a283f8a0684536bf844f166f4050d20473

Change-Id: I218b561bbe8c5f9c618afc771fc9fa9de2f5860e

Change-Id: Icc4e01bd7c5659801acbd370e616857916fede64

Change-Id: I1c533eef4399b66ca5bd59538b75bb37d1488690

The issue was related to some proxy that was getting deleted by
a slave inbetween two ClearInputs() SetInput() calls.
To solved that we use Reference count on the server side
to prevent object to be deleted if one client is still using it.
So now, each time a new client connect to the server, it increase
the reference count of the SIObjects that it is using.
In the case of a client crash a automatic garbage collection will
occurs and will decrease the reference count of the objects that
was still held by the client before the crash.

- Allow master to force participant to follow a given camera
- Keep a cache of all participant last camera position so when user switch
  from one camera to another, it get directly what the user is seeing.
- Camera position are only broadcasted at render time therefore a new-comer won't have any participant camera before they restart moving

- clients/master/slave management is done inside vtkSMCollaborationManager
  and Events are used to propagate the changes.
- pqServer/pqCollaborationManager convert those events to be full Qt signals
- Now when a client dies/disconnect all the clients are immediately aware
  and if needed a new master is elected.

- ProxyLocator are used to locate proxy and recreate them based on some
  state if they are not found.

- Loading state from protobuf message is slightly more compicated than
  the XML one, because a SubProxy do have their own state that is not
  shared with the root proxy like in XML. Therefore we have to deal
  with complex fetching/loading state. Using ProxyLocator simplify
  this dependancy mecanisme.
- Update the LoadState API to use ProxyLocator instead of StateLocator+Ctx

- Create Deserializer class hierarchy to handle Protobuf state and XML based state

  Instead of having a loadDefinitionOnly flag we use a full vtkObject as context object
  to identify in which context we want to load a given state. This allow us to skip
  property state loading as well as ignore_synchronization="1" tagged properties when
  a state come from another collaborating client.

This is used for vtkSMProxyManager and vtkSMProxyDefinitionManager

* Created new ParaViewCore directory in place of Servers.
* Moved classes from old directories to new ones.
* Removed some obsolete classes that were lingering in Filters/ServerManager.

- Bug #1: Proxy with sub-proxy that are references across properties
          were not happy when those sub-proxy were not available yet
          therefore the load state occurs in 2 steps. One we create
          the proxy/subProxy hierarchy with all globalID setup.
          Secondly we load the properties values.
- Bug #2: The delta computation in vtkSMProxyProperty and
          vtkSMInputProperty when a state was loaded was wrong when
          a proxy was deleted. We were skiping the test on the next
          one.

The CVS $Revision$ keyword replacement will no longer maintain these
macros automatically.  They were used only to implement CollectRevisions
and vtkObjectBase::PrintRevisions, an API that was never used.

Automated as follows:

  pass 0:
  catch templates
  ---------------
  $ git grep 'vtk\(Cxx\|Type\)RevisionMacro' | grep '<'

  pass 1:
  main changes
  ---------------
  $ git grep -l '^vtkCxxRevisionMacro' | while read file; do
    echo "$file" 1>&2
    perl -i -ne 'print unless (/^vtkCxxRevisionMacro/ and /\)/)' $file
  done
  $ git grep -l -e 'vtkTypeRevisionMacro(' | while read file; do
    echo "$file" 1>&2
    perl -i -pe 's/vtkTypeRevisionMacro/vtkTypeMacro/g' $file
  done

  pass 2:
  verify
  ---------------
  $ git grep 'vtk\(Cxx\|Type\)RevisionMacro'

Fixed multi-line vtkCxxRevisionMacro and templates by hand.

The CVS $Revision$ keyword replacement will no longer maintain these
macros automatically.  They were used only to implement CollectRevisions
and vtkObjectBase::PrintRevisions, an API that was never used.

Automated as follows:

  pass 0:
  catch templates
  ---------------
  $ git grep 'vtk\(Cxx\|Type\)RevisionMacro' | grep '<'

  pass 1:
  main changes
  ---------------
  $ git grep -l '^vtkCxxRevisionMacro' | while read file; do
    echo "$file" 1>&2
    perl -i -ne 'print unless (/^vtkCxxRevisionMacro/ and /\)/)' $file
  done
  $ git grep -l -e 'vtkTypeRevisionMacro(' | while read file; do
    echo "$file" 1>&2
    perl -i -pe 's/vtkTypeRevisionMacro/vtkTypeMacro/g' $file
  done

  pass 2:
  verify
  ---------------
  $ git grep 'vtk\(Cxx\|Type\)RevisionMacro'

Fixed multi-line vtkCxxRevisionMacro and templates by hand.

ENH: Add LANL's adaptive ParaView application. This adds multiresolution progression to streaming, such that the data is refined as is it displayed where it is most important to do so. The result is a low resolution initial view of the data, which is progressively filled in with more and more detail until all visible data is displayed at full resolution.

case when the view module is a comparative vis view.

No longer exposing "InteractorStyle" instead one should directly change the
camera manipulators. This makes life easier for comparative vis.

BUG: pvpython now accepts all command line arguments and simply transferts
them to the python interpretor.

BUG: pvpython now accepts all command line arguments and simply transferts
them to the python interpretor.