Update the api-version.xml file to reflect KitKat recent changes

This CL updates the api-versions.xml file, which is a file
used by Lint API check to check which API version each class,
field and method reference was introduced in.

It is generated by running sdk/apigenerator on an SDK install
which has android.jar from all 19 releases of Android installed.

This file was updated recently, but a few more APIs have changed
since then, so I regenerated it with the latest android.jar
snapshot.

Change-Id: If36a1df74c6bfabd9874a9d94b3725bf56bffcaa
merge in klp-release history after reset to klp-dev
Merge remote-tracking branch 'aosp/kitkat-mr1-release' into HEAD
development: TRDS 3.0 and new theme engine preparation (2/4)

For the one who do not know this feature see as reference
the first two versions here:

https://github.com/SlimRoms/frameworks_base/commit/b330fde28306286572ba390e451a72539c0c3576

https://github.com/SlimRoms/frameworks_base/commit/3194015737b7944b4185fca007b8d167a0675cd8

we got now over a year now a lot experience how to handle the qualifier fallback
as well how to theme it and how to handle other apps. Based on this knowledge we
redid some parts of TRDS engine with following new features/additions and fixes
to have now a final perfect working TRDS

- compared to the old versions where it was needed on some apps to restart them
  in background this is not needed any more. All is handled about the internal
  AOSP resource handling and on qualifier change the caches are cleared
  and the apps get an onconfigurationchanged to restart the activity
  like it is doing on orientation change eg
- inverted folder is now depreciated and the new folders are holodark
  and hololight which allows on the one hand a dark theme (at least
  how TRDS started) and a light based theme hololight
- This name change is mainly because of the new theme engine which
  will come which uses this as base to add 2 external themes at the same
  time and give the user the ability to switch between them. But this is
  still in early stages and this commit is just the preparation for it
- Two new automodes are now integrated. User can enable the twilight modus
  which enables/disables holodark/hololight depending on the daytime...means
  on the evening it switches to holodark on normal day it is hololight.
  The other automode is based on light conditions....means that if it is
  dark outside it switches to holodark....if we have bright light conditions
  it switches immediatelly to hololight. Due of the resource cache handling now
  this happens immediatelly for the user and feels completly system integrated
  and happens without delay. A bit comparable to some navigation tool for cars
  which can switch automatically from dark to light and back
- currently the auto modes as well the manual mode switches between holodark
  and hololight. Due that we do not have currently anything hololight themed
  in the source hololight = stock theme. We will give the user the ability
  later when done to choose between which modes the user want to switch
  (stock/holodark/hololight). But this does not make sense at the moment.
  As soon as we have done the light theme or theme engine (lets see what
  comes first) we will open the ability to choose it. This is only a small code change
- a lot small tweaks and fixes went as well into the new version

Whatever this commit as usual adds the support for it. The themeing is done in the
other commits by kroz which is as well way more extended then on the older versions

cheers

Change-Id: I33c814d2dac05154e840fb01a7009ad15451234e
Grant dev tools system permission to trigger media-scan service

Google add the action ACTION_MEDIA_MOUNT into the list of
protected boradcast, so that ordinary apps cannot trigger
media scanning by directly sending the action out. The system
built-in dev tool is granted system permission so that it
will not crash when executing media scaning tools.

Change-Id: I19797e61ba829df39d2b66f209cf41bf6565170f