Enforcement of platform size limitations is required

Memory ranges/sizes need to be checked to see whether they fit within the platform addressable ranges.

e.g. when installing the 32bit packages on a 64bit machine, there is no checking that the bucket size or per node quota fit within 32bit process constraints. There are also platform specific user space process addressable limits that need to be checks (e.g. Windows 32bit can address 2GB or 3GB depending on kernel configuration (4GT enabled or not)

1) ep_engine should refuse to start if the requested size is bigger than the current process memory space can accomodate
2) the GUI needs to be able to report that a engine didn't start, along with the reason
3) GUI process type bound checking shall be optional, initially just reporting engine failure is sufficient (as that is the more general mechanism that can also be used for other failures)