Don't load shared libraries in static builds.

Fixed vtkPVPluginLoader to not attempt to load shared libraries in a
static build of ParaView.

Change-Id: I3eddbc0c369431db9d0490881854cd42084164cc
Fixed issues with plugins and static pvserver.

The problem setup is this:

I have two local builds of ParaView, one static and one shared.
First, I connect with shared pvserver as (cs://localhost) and load some
distributed plugin (e.g. Moments) -- works as expected.

Next, I restart ParaView and connect to the static pvserver using the
same url (cs://localhost). Now attempting to load the same plugin will fail.

This happens because the client tells the server to load the plugin
configuration XML from its QSettings (since we want to restore auto-load
preferences, as well as extra use-loaded plugins). The second time, it
uses the XML obtained from the pvserver ran the first time (which was a
shared build) and hence has different paths for the plugins.

This interim fix addresses this issue by not overriding the paths the
server had determined. We need a cleaner fix for plugin configuration
management.

connect with the shared pvserver

Change-Id: Iaa7ce40928e34418ac59df9d23b04e704375db5d
Fix search path for ".plugins" in static builds.

On linux, with static builds when running from install dir, we need to
look for .plugins file in the lib directory, not the bin. This fixes
that.

Change-Id: I8ef91a85356566bb7738e749cadca3f3105054b9
Merge topic 'fix_static_plugins' into next

5956702f Fix search path for ".plugins" in static builds.
bd526f0b Fixed issues with plugins and static pvserver.
50a13f4a Don't load shared libraries in static builds.