Update common.xml

Proposal to add direct battery charge and energy consumption reporting in addition or instead of the current percentage of battery.  

The problem with the battery percentage is that the on-board system in most cases does not natively know the size of the energy storage and relies on the (possibly) configured battery capacity value.  In case of changing the battery on the field there may be different battery size or there may be a different type of power source on board. In any case, the percentage value is secondary information and dependent on a pre-configured capacity value, which may or may not be correct or relevant.  

If the on-board system has capability to report any consumption numbers, it almost certainly is measuring current and voltage samples.  These are primary information available to be reported and should be reported.

Possibly it could make sense to split message 147 to two separate messages: 1) multi-cell battery individual cell voltage reporting 2) total voltage & current readings and derivatives.
1. Fixed field closing tag.  2. Increased current and energy consumption field sizes.

Field size increase to accommodate kilowatt-size power trains and long missions. A more airlink economical option would be to use one scalar byte for both of the consumption fields.  However, not sure if the savings would carry their weight in added complexity.
Permits external m_mavlink_status array.
Added a message encoding function that accepts a channel.

In the C-API, just like there are the `mavlink_msg_msgname_pack` and `mavlink_msg_msgname_pack_chan` functions, there should be  `mavlink_msg_msgname_encode` and `mavlink_msg_msgname_encode_chan` functions, as not all messages are sent over the MAVLINK_COMM_0 channel and need the appropriate sequence number set.
pymavlink: fixed syntax error
pymavlink: raise version

fixing CRLF problem in zip file
Fix for documentation for RC_CHANNELS_OVERRIDE. See Github issue #72.
Replaced all occurances of 32767 & 65535 with INT16_MAX and UINT16_MAX. This makes it more clear that these aren't magic numbers. Additionally implies that the macros INT16_MAX/UINT16_MAX are to be used, which should be available in stdint.h.
Merge pull request #124 from Susurrus/override_fix

Override fix
Updated HIL message specifications to better meet demand, added helper functions to convert between Euler, Quaternions and rotation matrices (DCM), following NASA rotation standard and originally written (as attributed) by James Goppert.
Added copy step for conversions header, reverted HIL_STATE to original state, marked it as deprecated and added HIL_STATE_QUATERNION for the intended long-term message
Merge pull request #125 from mavlink/hil_fixes

Updated HIL message specifications to better meet demand, added helper functions for quaternions
Hotfix: Fixed unclear documentation
Fixed windows compile errors due to undefined constants
pymavlink: added more accurate altitude2 function
pymavlink: added ACRO and CRUISE modes
pymavlink: added wildcard support to mavflighttime.py
Merge pull request #123 from AutoQuad/upstream

Add some AutoQuad custom definitions and add autoquad.xml to CMakeLists
Merge pull request #120 from dimasad/master

Fixes in external rx buffer logic and adds possibility for external rx status
Merge pull request #121 from dimasad/msg_encode_chan

Added a message encoding function that accepts a channel.