Do not force WrappingTools library to be static
This library was originally forced to be static to ensure that the wrapping executables (vtkWrapPython, vtkWrapHierarchy, etc) were statically linked. The idea was that since the wrapping tools are used prior to installation, static linking was more robust, since otherwise they would have to rely on a baked-in RPATH.
However, these worries were unfounded, and it is simpler and more consistent for BUILD_SHARED to control whether WrappingTools is static.
There were also general complaints about static libs from some users (#17408 (closed)).