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.

ProxyListDomain were incorrectly registered, causing
memory leaks that were freed only when closing ParaView
This fixes it.

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

This adds support for plugin description in the plugin manager

Make pqDoubleLineEdit not use a format specific double validator.
pqDoubleLineEdit should always accept any valid double string. It should
only change how it's shown based on the chosen format.

Now, pqDoubleLineEdit also doesn't attempt to cleanup a number entered
by the user. Thus, if user enter `1e10` for the full precision text, the
full precision text stays as so.

Changed default precision used by the widget to mixed rather than fixed.

(cherry picked from commit b02aa392)

Make pqDoubleLineEdit not use a format specific double validator.
pqDoubleLineEdit should always accept any valid double string. It should
only change how it's shown based on the chosen format.

Now, pqDoubleLineEdit also doesn't attempt to cleanup a number entered
by the user. Thus, if user enter `1e10` for the full precision text, the
full precision text stays as so.

Changed default precision used by the widget to mixed rather than fixed.

 * 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)

This wil show the Lagrange cell type in the spreadsheet view.

This is a temporary fix for #18446. To make vtkSMViewProxy use offscreen
buffers for screen capture, we now support an environment variable
`PV_USE_OFFSCREEN_BUFFERS_FOR_IMAGE_CAPTURE`.

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.

Works similar to printfs %g format specifier.  Fixes #18483.

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.

Choices are
* Automatic, based on first time step
* Always 2D
* Always 3D

Use "|" as an internal separator instead of "_" because it is
less likely to collide with timestamp and filename characters. Also
automatically strip "*" from recovered writer input variable names.

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.

vtkSMDataDeliveryManager needs to keep track of lod/non-lod delivery
timestamps separately as the same delivery mode may be used for both.
Fixes #18419.

Fixes #18304.

Make pqDoubleLineEdit::RealNumberNotation enum values consistent with
those for vtkPVGeneralSettings enum values representing the same
notation. Also, re-order the enum options in settings.xml so that
Fixed and Scientific options are in the same order as
AnimationTimeNotation.

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.

When doing remote rendering, the client's mtime for when data delivery
happened was not correctly updated. That was causing the data delivery
logic to reexecute on each render. That was causing #18340.

Fixed vtkPVDataDeliveryManager to keep separate delivery objects for
each delivery mode. This ensures that the client doesn't end up with a
data delivery timestamp mismatch, as before. Also simplified the code in
general and adding timer log entries to catch such bug easily in the
future.

Fixes #18340.

`vtkPVRenderView::GetUseDistributedRenderingForStillRender` and
`vtkPVRenderView::GetUseDistributedRenderingForInteractiveRender` are
renamed to better reflect the implementation. These are not for still vs
interactive but full-res vs lod. New names avoid that confusion.