Fix multiple omnis issue

* Fixes #71 

Co-authored by: @NickMilef <milefn@rpi.edu> 

1) DeviceClient : not a module anymore, only stores device info
and holds callbacks

2) VRPNDeviceClient : subclasses DeviceClient AND Module, to
conserve the ability to run multiple clients in parallel with
a VRPN server

3) HDAPIDeviceServer : new module that manages the HDAPIDevice
clients execution, which need to be made sequentially. Also helps
managing a unique hdScheduler.

4) HDAPIDeviceClient : lets the HDAPIDeviceServer handle the
hdScheduler. Also makes use of hdMakeCurrentDevice.

5) SimulationManager : refactor to run modules instead of
deviceservers or deviceclients

6) Sandbox : use new simulationManager API to add modules

See merge request !99

Co-authored by: Nicholas Milef <milefn@rpi.edu>

1) DeviceClient : not a module anymore, only stores device info
and holds callbacks

2) VRPNDeviceClient : subclasses DeviceClient AND Module, to
conserve the ability to run multiple clients in parallel with
a VRPN server

3) HDAPIDeviceServer : new module that manages the HDAPIDevice
clients execution, which need to be made sequentially. Also helps
managing a unique hdScheduler.

4) HDAPIDeviceClient : lets the HDAPIDeviceServer handle the
hdScheduler. Also makes use of hdMakeCurrentDevice.

5) SimulationManager : refactor to run modules instead of
deviceservers or deviceclients

6) Sandbox : use new simulationManager API to add modules

Allows to use iMSTK as an external library
for other projects.

Documentation here:
https://cmake.org/cmake/help/git-master/manual/cmake-packages.7.html#creating-packages

COMP: correct ftd2xx & libusb install rules

Fixes #66 for ftd2xx

Also correct mismatch between static and shared with libusb.

See merge request !96

Fixes #66

COMP: Update to specific git_tags for external projects

Using a git branch name for an external project would update the repository of that external project when building iMSTK even though it would not be tested.

By hardcoding a certain commit #, we can make sure we need to specifically update the external project git_tag to update the external project.

This commit updates to the newer version of VegaFEM which should resolve the remaining issues on the Dashboard for Windows: iMSTK/VegaFEM-CMake@d1ab0858
> `export(PACKAGE VegaFEM)` was resulting in Vega being registered in a CMake Package Registry :
> https://cmake.org/Wiki/CMake/Tutorials/Package_Registry
> 
> Because of this, an incorrect version of VEGA could be directly linked against when doing `find_package(VegaFEM)`.
> 
> This should only be done when creating a package for installation:
> https://cmake.org/cmake/help/git-master/manual/cmake-packages.7.html#creating-packages

See merge request !94

Integrate the following commit:
iMSTK/VegaFEM-CMake@7bc1bda6

Also remove useless iMSTK_EXTERNAL_PROJECTS_PATHS
variable in External/CMakeLists.txt

Using a git branch name for an external project would
update the repository of that external project when
building iMSTK even though it would not be tested.

By hardcoding a certain commit #, we can make sure we
need to specifically update the external project git_tag
to update the external project.

This commit updates to the newer version of VegaFEM which
should resolve some errors:

iMSTK/VegaFEM-CMake@d1ab0858

COMP: fix ftd2xx.lib copy at compile time

On some windows systems, the command `cmake -E copy`
within `copy_ftd2xx_static_command` renames the ftd2xx.lib
file as `lib\${BUILD_TYPE}` instead of copying it within
the directory of the same name. Because of this, the directory
can not be created in the future for other libraries, explaining
the high number of compilation errors (~50)

Placing a `\` at the end of the destination directory should fix
this issue.

See merge request !93

On some windows systems, the command `cmake -E copy`
within `copy_ftd2xx_static_command` renames the ftd2xx.lib
file as `lib\${BUILD_TYPE}` instead of copying it within
the directory of the same name. Because of this, the directory
can not be created in the future for other libraries, explaining
the high number of compilation errors (~50)

COMP: Fix COMP errors with LibNiFalcon

LibNifalcon should link against ftd2xx and not libusb1 on Windows. Add ftd2xx as an external project (binaries).

Works with the newest versions of VRPN and LibNiFalcon.

See merge request !91

ENH: add support for dashboard

http://my.cdash.org/index.php?project=iMSTK

See merge request !92

http://my.cdash.org/index.php?project=iMSTK

LibNifalcon should link against ftd2xx and not libusb1
on Windows. Add ftd2xx as an external project (binaries).

Works with the newest versions of VRPN and LibNiFalcon

Correct comp linux

- Use CMake `CMAKE_CXX_STANDARD` to support C++11
- Check if `iMSTK_USE_OPENHAPTIC` is defined before using HDAPIDeviceClient in Sandbox
- Replace `itoa` (non standard) by `sprintf` in Sandbox
- Correct warnings in Sandbox

See merge request !90

itoa is not part of the standard library

Using CMAKE_CXX_STANDARD and THREADS_PREFER_PTHREAD_FLAG

Merge Refactoring into Master



See merge request !89

Merge Eti application into Refactoring



See merge request !88

- Fix workflow for PBD in SceneManager.cpp. Add/modify related functions for
PbdObject/PbdRigidObject/VirtualCoupleingPBDObject. It should work for the
most general case where collision/physics/visual meshes are different from
each other.
- Add LineMesh class and LineMeshRenderDelegate. Add support for LineMesh
class in imstkGeometry, imstkMesh, imstkRenderDelegate.

- Fix a bug for computeBoundingBox() in imstkMesh.
- Fix a bug for applying mapping in TetraTriangleMap.
- Fix a bug for computing the center of tetra in TetraTriangleMap.

	-Create PbdRigidObject class for objects that are not deformable but need
	to interact with deformable pbd objects.
	-Create VirtualCouplingPbdObject class, which is inherted from
	PbdRigidObject and TrackingController. The physics and colliding
	geometry(mesh) need to be translate/rotate manually to interact
	with deformable objects, which is different from existing
	VirtualCouplingObject class.

PBD examples not working properly due to issue related to mesh normals.

Conflicts:
	Base/Scene/imstkCollisionGraph.h
	Examples/Sandbox/main.cpp

Enforces style and place holders for comments in the pbd related code files

Style corrections2



See merge request !84

Add haptic device. Need to run in simulation mode, but rendering mesh in simulation mode is very low and results in huge amount of warnings