recovery: add overlay interface for recovery mode

Pan display needs FB allocation from driver and
since it is removed from driver, switching to overlay
interfaces in recovery mode. Basically forking out
the overlay and pan_display path in separate files.

Change-Id: I60f13e54befaa6da77e6c4d23399835509b41333
recovery: Add support for split display

Configure LEFT and RIGHT mixer separately
to drive high resolution display.

Change-Id: I3a3e6bffe6373caa991d9847dae6f2f4d8d20c48
recovery: Fix compilation for non MSM target

Make mdp5 version variable scope valid for non-MSM target.

Change-Id: Ib02c7d8f79c6d29e8f14b58810f628c3a80d416d
Fix overlay inclusion on MSM

Don't determine that target has an overlay if not using QCOM_BSP,
since most of the required functions will be dummied out

Change-Id: Ic2605baa00e629351bafa3f941c92f32d2155a4d
Fix mass storage in recovery

The proper order is mass_storage,adb. Some systems cannot recognize
the mass storage otherwise.

Change-Id: I7e240210adef52de70776353a3426e3fc3f1b5bc
fix merge error

Change-Id: Ibc6f22cf892cb2f1b7be5fa72c80dec1a142122a
use different USB PIDs for adb and adb+ums modes

Commit ad054c684524962eae3269c1d807dc60e8bca1ec made it so that
the same VID/PID pair was used for both adb and composite adb+ums
modes, which prevents the installation of drivers in Windows so that
either mode can be supported.

This uses the original VID/PID pair (18d1/d001) for adb+ums and
uses 18d1/d002 for adb.

Change-Id: I190c821995b7fe9e8177354aec70bd02c114d122
use correct USB PID for adb and new PID for adb+ums

The previous commit assumed that the correct PID for adb+ums
was 18d1/d001. That is incorrect. That VID/PID pair is widely
used for non-composite adb function in recovery. Since there is
no "generic Android" VID/PID allocated for adb+ums, we will
"unofficially reserve" an unused one for that purpose: 18d1/d003.

Change-Id: I6ae095569186c1e854f10b803f786d8c1ae7fb93
recovery: Compatibility with upstream minui change

 * minui is changing a lot upstream. We won't merge it here, but
   it's being used in another branch. Add compatibility in CWM
   so that we can move forward.

Change-Id: I8a3289df2d7bc569229b7212c22adb90d4e76ffd
2.8.0.0

Change-Id: I5beb8a2fb4ba84acad975a509e13f63a0170c4c4
syhost version

Change-Id: I9facd1ce26e0db4cfe7f7eb390688bba49f3bbae