BUG: 14760 Improved saving of settings file

- Added organization name member to vtkInitializationHelper
- Changed location of user settings file to
  CONFIG_DIR/ORGANIZATION_NAME/APPLICATION_NAME-UserSettings.json
  This will enable the same organization to have more than one
  branded ParaView application with different settings.
- Creates the directory in which the settings file should
  reside if it does not exist.
- Application and organization names are set in pqApplicationCore
  instead of branded_paraview_initializer.cxx.in

Change-Id: Ic50a020c8acf984c2284e824fa99145a93ad028e
Save settings file only when a setting has been modified

Also, fixed a bug where settings with default values were being saved
to the settings file.

Change-Id: Ia3908b94678b1828c89d7ef4090bebc54d43e4d4
Change how colors are stored in pqColorChooserButton.

Colors were stored in a QColor. Internally, QColor stores color
components as 16-bit unsigned ints. The Qt documentation of
QColor states the consequence of this:

"QColor supports floating point precision and provides floating point
versions of all the color components functions, e.g.getRgbF(), hueF()
and fromCmykF(). Note that since the components are stored using
16-bit integers, there might be minor deviations between the values
set using, for example, setRgbF() and the values returned by the
getRgbF() function due to rounding."

Because the value retrieved from the QColor might not be the same as
what was input, any color property passed through a QColor could be
slightly different from the default color property, causing the color
to be saved as a custom setting in the settings JSON file when doing
so wasn't warranted.

This is solved by storing the RGBA color components in
pqColorChooserButton as an array of doubles instead of in a QColor
object.

Change-Id: I750b991cbb17c3b8c4aeb6fb02b0c2936e0bca2f
Change default application name

Changed default name to GenericParaViewApplication in the
initialization helper to prevent any accidental reading/writing of
ParaView's settings file by branded applications.

Change-Id: I1d4b3e7df383a070df5b4c83db8de88a944d6316
Added XML attribute "both" for hint SaveInQSettings

If set to 1, this attribute indicates that the property value should
be saved in both QSettings and the user settings JSON file. Defaults
to 0 (save only in QSettings) if attribute is not present.

Change-Id: Ieb0b871a3c8603cf67659b59973e71c0cafc4828
Cleaned up JSON settings file when proxy group is empty

When a proxy group is empty, it is removed from the root JSON value.
Also, fixed a bug where plain old vtkSMProperties were not handled
correctly (they should not be written to/read from file). Did this by
adding boolean return values to SetPropertySetting() and
SetProxySetting() methods where true indicates the setting of values
was successful and false indicates failure.

Change-Id: I20bbd35a5dea3c63b4d62e2a31e7691c74564175
Fix pqProxyWidgetDialog to activate OK button when enter is pressed

Change-Id: I3766b8805b4e71985b4faf2305815f0067ecf2ac
BUG #14729: Fix remote rendering when rendering image volumes.

vtkPVDataDeliveryManager was using incorrect geometry size for
vtkImageVolumeRepresentation. vtkImageVolumeRepresentation needed to
report the true data size to vtkPVDataDeliveryManager for it make the
correct decision. This commit fixes that by adding an API to
vtkPVDataDeliveryManager to pass in a "true-data-size" when passing
dataset to deliver.

Change-Id: Iff1bc45e18f35b1bf1c57739b23daa7441c5ecd8
BUG #13804: Added support to show rendering information.

Added annotations to Render View to show information about the most
recent render including things like whether LOD was used, whether
remote rendering was used, and the frame rate.

To view this widget, go to the Settings dialog and on the "Render View"
tab, search of "annotation". Turn the "Set whether to see annotation..."
setting on to see this information popup in the render view.

Change-Id: I6986ee5964705470d061c18a2e875367cf3659af
Minor tweaks to pqQuickLaunchDialog.

Making the dialog a little bigger and allowing resizing.

Change-Id: I8a6dd533b045bfe33f92b3fe961a9aa9837f2665
BUG #14244: Fix stereo image capture.

Bring in VTK fix for the bug. At the same time, addresses other errors
raised when saving stereo image as the default stereo type ended up
being set to CrystalEyes.

Change-Id: I15b949fdf0587b1bb14117082dff4db3a9870d0b
Got initial addition of min/max as labels working

Constraints in horizontal orientation need to be added to keep min/max
labels from overlapping others.

Change-Id: I31e0a26655cd7744421c2ba798fa9ab336a4bdd5
In horizontal orientation, change justification of min/max labels

Use right justification on the left side, right justification on the
left. This moves the large min/max labels outside the scalar bar
and prevents them from overlapping the other "nice" labels.

Change-Id: I18297dda57d9ac12228a887f193b5132ebc1f32f
Turn off visibility of labels that overlap min/max labels

Change-Id: Ife1dfc5ea581c73ab1ccde93ed9379f73b71c5d8
Draw major ticks only for labels that are visible

Change-Id: I5606fd947206f6454f758a72caf928db0385777a
Made min/max labels optional and added formatting string for them

Change-Id: Ie4c02f641a43829a1f0bec8d55dbe4bf3589b740
Added test for min/max labels in color legend

Change-Id: I7096749bd39cf1dcd8a8113871d5fe378ee13155
Fixed a few shadowed variable and unused variable warnings

Change-Id: I84e729c653e0c16c7303d735a5d5b692ecd1535b
Fix formatting of labels with exponents on Windows

The exponent of numbers formatted with the *printf* family of functions
has 3 digits on Windows but only 2 on all other systems. Fixed
this with Win32-specific code.

Change-Id: I00afd0a5926bc7bf4088faf5e54a5559d27701ca
pv*server: load plugins in the data and render servers

Change-Id: I16f98a56b9ad6fca1dc718346d0bdf18ce4b862d