aravis: set a sensible framerate when going to cont. software trigger mode
0.7.0 release info
aravis: depend on 0.1.12 and bump ver to 0.7.1
use new aravis 0.1.12 API
Fix many (all) enumeration / race bugs

The symptom was corrupted communications when enumerating
many cameras.

The root cause was during enumeration there is multiple
arv_cameras created and never unreffed and importantly,
the stream is never started on them. While I am not
convinced this isnt a bug in aravis (unstarted cameras should
not eat data), it is safest to unref and thus cleanup those
cameras we enumerate but do not start streaming with.

Unfortunately this means we lose some cam_info granualarity,
(I don't fill out the vendor and model, only the chip/guid),
but at least it works now
aravis: save the camera mfg. and the guid (chip)
version bump -> 0.7.2
aravis: set the ROI to max by default
set to highest continuous framerate at startup
0.7.3 release info
Ignore Fake

Use the arv_interface_XXX functions for camera enumeration
Fix building against uninstalled aravis
Fix running against aravis>0.12
API/ABI Break

Add an additional construction parameter - a const char *
to specify the interface on the host machine used to communicate
with the camera. The meaning is backend dependent. For example,
in the aravis case, the interface is a ip address of the interface
used to communicate with the camera.

It is OK to pass NULL for this value.

Only the aravis backend understands this new argument.
enable runtime debugging of libcamiface/aravis

Set the LIBCAMIFACE_ARAVIS_DEBUG env var
Support the interface constructor property in the aravis backend

Allows binding cameras to specific network interface ports
aravis: improve debugging
aravis: improved debugging
aravis: add environment variable for resend behaviour
aravis: allow increasing packet size using LIBCAMIFACE_ARAVIS_PACKET_SIZE