Fix reader's association with file extensions in the GUI dialog.

Readers that were available through the GUI file open dialog
were specified based on the client side build, including plugins.
So even though a reader on the server may be available it was
the client that was determining which readers it thought should
be used for opening a file on the server. Thus, if any reader
depended directly on MPI it wouldn't be available on the client
if the client was built in serial. This change fixes that so that
the assocation of file extensions to readers was based on the
server's servermanager XML.

Change-Id: Ie7cf4fd3caaa3bd2dfcf17a33baa5b9c69072af5
Changing reader plugins to incorporate being only needed on the server.

In the previous commitI made it possible for reader plugins to
work properly when it is only defined on the server. Now I'm
changing the plugins (besides the nektar reader plugin) to
take advantage of that.

Change-Id: Ibf7836fbc54e9cd1fed192203f48a162ccd98a14
Fixes to vtkSMReaderFactory.

Added the ability to add and remove groups to search for readers
in. Also fixed a Python bug for a class that got removed.

Change-Id: Ifbfca572e5a473363e6da3a7a302424dc2246fc8
Changing the writers to be available on the client based on server XML.

Same changes that I just did for readers to make them only defined
on the server and then pass that info to the client. Also removed
the GMVReader plugin's GUI XML that isn't needed. Finally, added
in warnings for both reader and writer plugins that still define
the GUI XML stuff instead of putting the hints in the server
side XML Hints section.

Change-Id: Idbf592f0cebcb69a214e1677743cf64318110380
Merge topic 'serverside_only_reader' into next

d23fc9e Changing the writers to be available on the client based on server XML.
7a5de17 Fixes to vtkSMReaderFactory.
5627d44 Changing reader plugins to incorporate being only needed on the server.
e675269 Fix reader's association with file extensions in the GUI dialog.
BUG #14204. Refactor domains and domain-update logic.

This commit refactors the domains in ServerManager. Domain are no longer
expected to be updated by the application manually
(vtkSMProperty::UpdateDependentDomains() has been deprecated). Instead, whenever
a property is modified (rather its unchecked values are modified), the depedent
domains are automatically updated.

vtkSMDomain subclasses have been updated to fire DomainModifiedEvent only when
the domain actually changes. Next, we can update the Qt layer to simplify
handling domains.

This commit also includes some restructuring of the vtkSMDomain hierarchy.

vtkSMDoubleRangeDomain and vtkSMIntRangeDomain are now just template
specializations of vtkSMRangeDomainTemplate (instead of duplicated logic).

vtkSMArraySelectionDomain is now simply an empty subclass of
vtkStringListDomain. It didn't need any custom logic.

Also removed unused domains: vtkSMNumberOfGroupsDomaini,a nd
vtkSMStringListRangeDomain.

Deleting vtkSMPropertyAdaptor. One can use vtkSMPropertyHelper instead.

Change-Id: Ib227082b3eeea6af89db5ccd0a7f0d539e1abce2
Merge topic '14204_fix_domains' into next

4b3af8b BUG #14204. Refactor domains and domain-update logic.
Update to VTK master

Change-Id: Ie868c429bd67fc9d6240e906078459c2ed94dd70
Update manifest after changes to VTK.

Change-Id: Ieafa33c1e078effab539824df3c6b95f583ed99f
Merge topic 'update_to_master' into next

4806ff3 Update manifest after changes to VTK.
8030ec0 Update to VTK master
Fix build issues on windows with template instantiation.

Follow the pattern used by vtkDataArrayTemplate to overcome these issues.

Change-Id: I7215b1a5b373c72065d8df9df5313ad5b3e4a340
Merge topic '14204_fix_domains' into next

ecbfc4c Fix build issues on windows with template instantiation.
Fix colormap test playback.

Change-Id: I7ce7d4dc985826eb43cd4c72586209ee4565a15d
Merge topic '14204_fix_domains' into next

20e7d2e Fix colormap test playback.