[TIMOB-2375] Android: If "density images" are used but anyDensity set to false in manifest, show warning at build time

(from [9985f8f908c01a722823bec6d4cd34df97c198c1]) [#1594 state:resolved] Map entries from tiapp.xml into the generated AndroidManifest.xml, including any attributes thate are put on to the and elements in tiapp.xml. Differentiate between stuff that's additive (such as entries) versus stuff that needs to replace entries in the manifest because they only appear once (<uses-sdk> and <supports-screens>). [#2375 state:resolved] Show warning during build if density-specific images are present but anyDensity="true" is not set. https://github.com/appcelerator/titanium_mobile/commit/9985f8f908c01a722823bec6d4cd34df97c198c1"> https://github.com/appcelerator/titanium_mobile/commit/9985f8f908c0...

(from [eecd982e9e9df75098ded4415f12be2e0a25a8aa]) [#1594 state:resolved] Be sure to only try to merge manifest info from tiapp into actual manifest if the tiapp.py parser actually found a entry. [#2375 state:resolved] Hard-code suppression of the anyDensity warning for when KitchenSink is running, so as to not freak everybody out. The density-specific image folder is in KS just to test loading from res/drawable. https://github.com/appcelerator/titanium_mobile/commit/eecd982e9e9df75098ded4415f12be2e0a25a8aa"> https://github.com/appcelerator/titanium_mobile/commit/eecd982e9e9d...