fb: controll user case when user freeze or uninstalls or reinstall apps

till now on navbar navring or powermenu it still shows the app icon
or it does not show any icon after reboot. For UX it is way better
to clearly show the User that she/he has disabled or uninstalled an app
which is binded. If this is the case the Icon changes to the error
none icon....on PowerMenu as well in settings and Error string will be shown
So the user clearly know that he either needs to bind this action to another
one. Or to restore the accidentaly removed app. If the user restores the
Icon of course it shows immediately again up

As well I removed the observer for shortcuts widgets completly and moved
the observing values into the already existend PhoneStatusBar observer.
So we do not have currently on all the systemUI another one then the
actual from AOSP

Change-Id: I25623dc12ba4c1ae6ee6a106aa903d3c28c92a92

Conflicts:
	core/java/com/android/internal/util/slim/AppHelper.java
	core/java/com/android/internal/util/slim/PolicyHelper.java
	packages/SystemUI/src/com/android/systemui/SearchPanelView.java
	packages/SystemUI/src/com/android/systemui/statusbar/phone/NavigationBarView.java
	packages/SystemUI/src/com/android/systemui/statusbar/phone/PhoneStatusBar.java
fb: navigationbar use always slimactions and add contentdescription

No need to use the AOSP implementation at all...we can send all actions
over SlimActions....so remove AOSP implementation and clean up

As well add contentdescription for accessibility events like talkback
for ppl who are not able to see. Gives the user all information back
needed.

Change-Id: I8f82f1139f1248d9cf8e762d6669bb75ae4e205f

Conflicts:
	packages/SystemUI/src/com/android/systemui/statusbar/phone/NavigationBarView.java
fb: small cleanup and fixes in navbar transitions

this commit fixes several things

- cleanup: no need to go every time trough all calculations if back
button is not present

- force to set alpha value for backbutton on disableflag
changes (merge derp from 4.4.1 merge)

- new introduced workaround from google to animate the altbackkey->backkey
on password lockscreen should not depend on home button view existence and
should only call for the respective disable flags which are always present
from the system. As well which is needed for our navbar call the animation
values from whatever button is existend which behaves like home (so all buttons
only recents and back button not)

whatever still to do if the user uses password as keyguard method
google introduced a workaround to give the altbackicon->backicon
same transition then all other icons....but this workaround is not
really good working and has off timings compared to the other buttons.
Will be fixed in a seperate patchset and should be submitted back to
google as well.

Change-Id: I2c3135b7eb3b87042b757c422f77ef9f5ed280a3

Conflicts:
	packages/SystemUI/src/com/android/systemui/statusbar/phone/NavigationBarView.java