CameraFeedback: added CAMERA_FEEDBACK_FLAGS for open/closed loop

This is so a GCS can tell if a certain picture was definitely captured
(e.g. with a CCB or machine vision cam) or only requested in the blink
(e.g. uni-directional CHDK)
GCS_MAVLink: regenerate mavlink headers
AP_Math: Comments on WGS coordinate conversions
AP_NOTIFY: RTK GPS visual notification through faster blink
SITL: Piksi Heartbeat Message support, Integer-RTK baseline simulation
AP_GPS: SwiftNav RTK Driver and GPS AutoSwitch param
ArduCopter: GPS Callback for calculating base position
MAVLink: New message definitions for GPS_RTK
GCS_MAVLink: Add support for GPS_RTK messages
AP_GPS: GPS calculates MAVLink messages for GPS and GPS_RTK
ArduCopter: Move MAVLink size check into library
GCS_MAVLink: regenerate headers
GCS_MAVLink: fixed flymaple build

has dual GPS but no RTK support
AP_GPS: fixed build errors and warnings in SBP driver

shadowed variables and implied casts in structures
GCS_MAVLink: added missing RTK headers
GCS_MAVLink: fixed a shadowed variable
tools: Change LogAnalyzer tabs to spaces (per APM python conventions)
CameraFeedback: alt rel/msl, renamed CAMERA_EVENT

- include both “alt_msl” and “alt_rel”
- rename CAMERA_EVENT to CAMERA_STATUS
- clarify comments regarding message origin and order
- change pitch/roll/yaw to be camera rather than vehicle, earth frame
GCS_MAVLink: regenerate headers
tools: Allow LogAnalyzer to read from stdin rather than just files

Use - intead of the filename