A few files in VTK require the fix as well.
Fix a doc typo.

Commit fbe0c3b4 accidentally made the parallel XML writers only
available in serial so this now makes them available in serial
and parallel.

If writing multiple time steps and trying to write to the current
directory the vtkFileSeriesWriter will try to write to / instead.

The parallel XML writers should be available for saving data in the
GUI as well as with the Python SaveData() method when the server is
also a single process so that things like traces and then running
the Python script later on work regardless of the number of MPI
processes.

CinemaExporter is unrelated with VTKExtensionsRendering.
This split removes a PythonInterpreter dependency for VTKExtensionsRendering.

When the Appender was used (Input was not an UnstructuredGrid) the input could either be a dataset or a CompositeDataset.
That switch was not taking care and a NULL pointer could be wrongly accessed.

This patch make sure we pass the data from a valid DataObject.

Added "Output Data Set Type" property. Updated and corrected the
documentation as well.

If the ExtractSurfaces option is on, this filter produces a single
vtkPolyData output from the surfaces extracted from blocks in the
input. If off, the filter produces a single vtkUnstructuredGrid output
from the entire blocks in the input.

This class is now used for the "Merge Blocks" filter in ParaView.

It is an integration parameter after all, so it should not be under
the Streamline Parameters group.

otherwise, we get SIProxy shouldn't be null assert failures in the
client+renderserver+dataserver tests where dataserver tries
to instantiate the state.

note: this has been broken since PV 5.5.0

Replace int with vtkIdType in key places to enable reading files
supported up to the maximum size supported by the format.

Thanks to Erik Keever, whose patch was the starting point for this
change.

The vtkPointGaussianRepresentation was always creating a vtkPolyData
on the client, which caused the data delivery mechanism to not copy
and data for local rendering. Fixed this by always producing a
vtkMultiBlockDataSet on the client and server. If the input is a
vtkDataSet, a vtkMultiBlockDataSet is created as the output and it's
child is a vtkPolyData with the points and point data from the
vtkDataSet.

We want to allow the Multiblock writer to be able to write HTG blocks in serial.
But in parallel when we have a distributed HTG we only want to have the phtg writer.

Therefore we extended the XML definition to only support HTG in serial for MultiBlock.

Allow htg's to pass through vtkCompleteArrays filter

Updating the constructor of vtkPVDataInformation to use static
member initialization instead.

This adds a plugin that expose filters to convert from and to
explicit structured grid, as well as a crop filter.
This also add tests for these filters.

This add support for the new vtkExplicitStructuredGrid datatype in :
 - vtkPVDataInformation for displaying information
 - vtkPVGeometryFilter in order to use the correct geoemtry filter

The box drawn for zoom-to-box, by default, is anchored at the start point
as one of the corner points. One can make it centereda at the
interaction start point instead by using the Ctrl or Shift key
modifiers.

fixes #18898.

pqDoubleVectorPropertyWidget now supports adding a button to reset the
bounds to active data bounds. The AxesGrid panel uses this new button to
make it easy for users to setup the bounds using the current data
source.

hide font properties from default view to make the panel simpler (and
easier to access data bounds related properties).

vtkPVGridAxes3DActor now support explicit bounds.

makes it easier to support coloring contours.

using new API on `vtkDataObject` to get vtkDataSetAttributes object for
right type.

vtkPVContourFilter now explicitly cleans the output array for scalars
used to generate the contour to set them to precisely match the
requested contour values. This makes it possible to identify each
contour surface/line uniquely.

The box drawn for zoom-to-box, by default, is anchored at the start point
as one of the corner points. One can make it centereda at the
interaction start point instead by using the Ctrl or Shift key
modifiers.

fixes #18898.

An error in logic meant the loop would only execute once, resulting in
an unreachable code warning. Fix the unconditional return at the end
of the loop.

These additional settings offer control over how points and lines are
offset in addition to the previous settings for polygon
offset. Improved the description of the properties as well, and set
better defaults.

Hat tip to Ken Martin <ken.martin@kitware.com> for the suggested
defaults.

Also solves a -Wmisleading-indentation warning.

These are unneeded and lead to warnings with -Wignored-qualifiers on.