The check to determine the version of VTK-m from git was duplicated in
CMakeLists.txt. Although pointless, it generally was not a big deal
(only an extra check when running CMake). Except for some reason with
the latest changes to the CMake build the second time find_package(Git)
was called on my system the GIT_EXECUTABLE variable got cleared out and
that caused the configure to fail. I have no idea why this happens (and
running CMake again seems to fix the problem), but simply removing the
extraneous find seems fix the problem.

Found via `codespell -q 3` via downstream VTK

Projects might want to force these without giving users the indication
that their choices actually matter.

Most of the code was unneeded as the primitive types have a minimum required
size that we can rely on.

Projects might want to force these without giving users the indication
that their choices actually matter.

It's an internal detail and if it doesn't exist, it is handled properly.

The benchmarking isn't installed as part of vtk-m and therefore shouldn't
be under vtkm/

This way in the future it is easier to make currently mutually exclusive
compile options be all enabled at the same time.

Adding option to enable MPI. When enabled, we do `find_package(MPI)` in
the Base component itself.

Ported cpu vectorization flags over to new CMake file called CPUVectorization.cmake and refactored some of the logic to use an interface lib.

VTK doesn't hide symbols for static builds, which results in linker
errors for VTK targets that link with VTK-m. This option allows VTK-m
to match VTK's behavior.

added doxyfile and vtkmBuildDocumentation.cmake back into the build process and tested that they built out the html docs.

Obviously this does mean that CUDA is not supported with 3.3.

This is causing issues when building ParaView with VTK-m and VTK
kits enabled.

Files like VTKmConfig.cmake are now under:

prefix/lib/cmake/vtkm-1.0/, rather than
prefix/lib

to allow multiple vtkm versions to share an installation prefix.

Sandia National Laboratories recently changed management from the
Sandia Corporation to the National Technology & Engineering Solutions
of Sandia, LLC (NTESS). The copyright statements need to be updated
accordingly.

When used as a submodule, redefining LIBRARY_OUTPUT_PATH and
EXECUTABLE_OUTPUT_PATH fails since the CMake default variables from the
containing project already exist.

This was requested by ParaView for performance reasons.

CMake has several default build types, but if nothing is specified when
configuring your project it defaults to an empty string and no optimization
flags are used.

It will now default to using a debug build if the source directory is a git
clone, or a release build if not. Additionally when using ccmake or cmake-gui
this will provide a nice list of possible options for CMAKE_BUILD_TYPE.