Windows

Hi Jörg,

Your LabViewGitEnv tool is helpful, and I wanted to extend it in two ways:

1. Allow a new user/contributor to install the scripts independently from cloning.
  * Rather than directly clone into `/usr/local`, a contributor might want to clone into a dedicated workspace so that they can control when their changes are propagated to their environment. My proposed change keeps the existing clone-to-install behavior, but also adds an explicit-install script.
2. Detect the version and bitness of LabVIEW to use for LVCompare and LVMerge.
  * Many of the LabViewGitEnv forks update `LVConfig.sh` to match their version and bitness of LabVIEW. My proposed change uses a tool from [VIKit](https://github.com/wireddown/VIKit) to find a matching or newer version of LabVIEW to use. If the tool is not installed, LabViewGitEnv uses the explicit versions in LVConfig.sh.

The first change summarized:
* Move much of the logic in `bin/LVInit.sh` to functions in new file `etc/LVUtilities.sh`.
* Add new file `bin/LVBootstrap.sh`.

The second change summarized:
* Add new file `etc/LVDetect.sh`, which has a function called `detect_labview_version`.
* Source LVDetect.sh in `etc/LVConfig.sh` so the diff and merge wrapper scripts can use it.

Finally, I updated a few words for spelling and changed Bash variable references to ${CurlyBraces}.