Implementations of Binning Property in camera adapters

[nicost]

Related to PR #811. Observations how cameras currently implement the binning property:

AmScope: Binning is a String property, with values 1x1, 2x2, 4x4. OK
Andor: Integer property, default "1" OK
AndorSDK3: String property, default "1x1" OK
Aravis: Integer Property, default "1" OK
ArduinoCounter: Integer Property, default "1" OK
Atik: Integer Property, default "1" OK
Basler: Integer Property, default "1" OK
BaumerOptronics: Integer Property, default "1" OK
DahengGalaxy: String property, default "1" Not OK, breaks
DemoCamera: Integer Property, default "1" OK
FLICamera, Integer Property OK
FakeCamera: Integer property
Fli: Integer property
GigECamera: Interegr Property
HikRobot: Integer property
IDSPeak: Integer Property
IDS_uEye: String Property, I believe it uses 1x1
IIDC: Integer property
JAI: Integer Property
Lumenera: Integer property
MatrixVision: String Property, 1x1
Mightex_C_Cam: Intereger Property
Mightex_SB_Cam: Integer Property
Motic: Integer Property
NikonKs: Integer property
OpenCVGrabber: Integer
PCO_Generic: Integer
PICAM: Integer
PVCAM: String, values can be 1x1, 1x4, and 1, 2, etc.. Not OK
Piper: Integer property
PixelLink: String property . Unclear Possibly not OK
PlayerOne: Integer
PointGrey: Integer
PrincetonInstruments: Integer
PyDevice: Values are 1, not sure how the property is defined
QCam: Integer
QSI: Integer
RaptorEpix: Integer
Revealer: Integer
ScionCam:
SensiCam: Integer
SequenceTester: Integer
SigmaKoki: Integer
SimpleCam: Integer
Spinnaker: Integer
Spot: Integer
TISCam: Integer
TSI: Integer
TUCam: String, weird, high number, this one will break, but that is what started this whole endavour.
TeensyPulseGenerator: Integer
ThorlabsUSBCamera: Integer
TwainCamera: Integer
TwoPhoton: Integer
UniversalMMHubUSB: Unclear
Utilities-MultiCamera: Integer
Video4Linux: Integer
Ximea: Integer
ZWO: Integer
dc1394: Unclear