FontFile properties didn't have default_values specified, which caused
them to traced always. Fixed that by assigning default value.

expose some mapper parameters:
 - atoms/bonds visiblity,
 - radius values/scale/type

presets are also available from proxy

Also modified Threshold.xml test to exercise the new option.

This adds two new uniform glyphing modes to the vtkPVGlyphFilter and also generalizes a bit its API.
The two new modes are based on "inverse transform sampling" algorithm, the first one uses surface area, the second one uses cell volume.

The surface one will actually extract the surface first if needed, so the glyphs will be located on the surface mesh only.
The volume one will ignore completely non-3D cells.

Both modes support multiblocks and parallel meshes perfectly, as well as cell centers when using cell data.

Those modes were needed because the current algorithm is only based on the mesh bounds and this have limitations and bad behaviors, especially when dealing with multi pieces mesh.

The propery values are set through the Annotations table in the Color
Map Editor, so it need not be displayed in its own table.

vtkSMFieldDataDomain no longer updates itself based on input type. That
was generally not useful and added unnecessary complication to the
domain and the corresponding UI. Cleaned that up.

vtkSMFieldDataDomain now raises warnings if used in
vtkSMStringVectorProperty as we tended to do in the past.

vtkSMFieldDataDomain was used on vtkSMStringVectorProperty instances
that allowed user to select array to process. There is really no need
for it nor is it correct, since vtkSMFieldDataDomain is a subclass of
vtkSMEnumerationDomain and hence intended for vtkSMIntVectorProperty
instances!

Getting rid of this old misuse of the domain.

Adding pqPauseLiveSourcePropertyWidget which can be used to add UI
button to pause/resume live source updates.

The `LiveProgrammableSource` adds this widget to its properties to allow
users to pause (and also act as an example of how to use this widget).

pqProxyWidget supports groups to group multiple properties together.
When that happens, if the same group is listed multiple times with
different set of properties, the UI showed it as separate groups. It's
better if all properties in the group with the same label are clubbed
together. This fixes that.

Also cleaned up implementation in pqProxyWidget for creating widget to
be a bit easier to read.

Better default configuration now managed by the domain
Multiple corrections to the widget/dialog duality
Added a "Reset to domain" button
Updated tests
Fix #18561

Some property name contains spaces. This remove the spaces from these property if they have not been in a release yet.

A new ColorSpace has been added in VTK, this uses it.
This add a few Step Color Map preset
This adds also .md and test

This property was used to pick which component to sort by. Since we are
now splitting multicomponent arrays into separate arrays, this is no
longer necessary.

MergePoint property did not have a correct name

 * Exposing new PointCellData conversion option

 In VTK, the PointData to CellData and CellData to PointData filters
 just got new properties to be able to only process certain arrays
 instead of systematically processing all arrays. We expose
 the properties in the xml of these filter so they can be used
 in ParaView. This also addd a test for PointCellData conversion.

 * Using these properties with AutoConvert properties
 AutoConvert properties settings allows user to use
 some filter with Point/Cell data filters even when
 they do not accept it. The conversion is done
 in vtkPVPostFilter but it uses to convert all
 arrays instead of only the needed one.
 This uses the new PointData to CellData and CellData to
 PointData filter properties to be able to convert
 only the needed arrays.

cinema A does not yet support pose cameras and only the pose cameras
suppport tracking and roll. This change makes it harder for the user
to try those combinations and handles with a message invalid
combinations when they are made.

note: constraining the camera model GUI to only have static and phi
theta when in non-composite mode would be better but doing that would
require a custom decorator.

Revert back to a simple scale factor for controlling overall glyph
size and remove the data rescaling feature that mapped data values
linearly to a range of vector sizes.

Also rearrange UI components so that the orientation array is above
scale options and glyph transform properties are after everything
else.

(cherry picked from commit f5f86046)

Revert back to a simple scale factor for controlling overall glyph
size and remove the data rescaling feature that mapped data values
linearly to a range of vector sizes.

Also rearrange UI components so that the orientation array is above
scale options and glyph transform properties are after everything
else.

two new pieces of global state:
 time compartment size, the number of ranks to use per timestep
 input filepattern for readers that begin the pipeline

input filepattern used to be per source, and was specified via
the channel matching section of the dialog. Per discussion with Andy
multiple readers are not really well supported anyway so simplify
to a global filepattern.

fixed some bugs in the original plugin that this deprecates, involving
a lookup into map of views that failed with no name, and code rot
where the base paraview python API changed and made it incompatible

this is continuation of changes in 7eb49c63. the commit missed removing
the lights properties from Comparative Render View and they were being
shown on the properties panel erroneously. fixed that.

fixes #18231.

introduced accidentally in commit 78432508 "implementation revisions ..."

This also allows us to add a more efficient code path, using memcpy,
when only the X array is generated.

Fixes #18427

Previous logic was scaling poorly
Also:
* Expose options to enable/disable SMP and set "desired bytes per piece"
* Change paraview source name to "Fast Uniform Grid"
* Change whole extent property to non-advanced

Also add a test for the feature.

This is a better separation of regular and catalyst export
definitions. The catalyst specific state is no longer on the
regular writer and screenshot definitions. Instead we have
a new catalyst specific groups where in we use proxy inheritance
to add catalyst specific properties to the normal export proxy
definitions. With this the catalyst and cinema specific writers
and properties no longer show up in regular export dialogs.

It was possible that the UI elements controlling glyph scaling
wouldn't be shown when an array with one component was selected as the
ScaleArray. This would happen when the VectorScaleMode was set to
"Scale by Components". Fixed some logic to prevent that from
happening.

Show a "cancel" icon (circle with line through it) to indicate the
"none" array type. Make the none string for ScaleArray and
OrientationArray in the Glyph filter variants clearer ("No scale
array" and "No orientation array", respectively).