fb: Keyguard disable challenge drag down on slimpin/simpuk screen

On simpin, simpuck and as well account change screen it does not make
any sense to give the user the abillity to drag down the challenge to show
the widget maximized (neither if widgets are enabled or disabled)
Reason: simpin/simpuck widget is not shown due of security reasons
and on account change the next expected behaviour is that the user gets a new
setup. So it does not make in this case as well sense

Just check for current securityscreen selection to block this behaviour. As
well move the enable/disable code to a proper place

Change-Id: I0b16d1e590252b537d6c71c4aa9b133ed832be45
Keyguard: do not show maximized on simpin and several fixes

- to show a maximzed widget container on first boot when simpin
  or puk is requested does not make any sense. In this case
  show it as normal view
- fix sometimes unresponsive unlock handle on maximized widgets
  and bring it to front (happened only in combination with
  lock before unlock)
- a bit codecleanup and centralize
- fix animation was visible on screnn turn on. Now it is directly
  maximized visible

Change-Id: I9ba5d8f9537c68d3590826eb8d1483a02cfe3266

This also includes:
Keyguard: Ensure that a widget and page is attached before attaching
https://github.com/SlimRoms/frameworks_base/commit/d0d65cc6da6723b137ad0fe1bbd4d15463262a3c
Telephony: Modify code to check that PUK code length is always 8.

As per 3GPP TS 31.101 Release 11 section 9.6, the number of digits
for UNBLOCK PIN (PUK) is always 8.

Change-Id: I4ea69fd8e2e8e96330d10a67b2d1f5a1859c1016
Framework: disable keyguard widget frame (1/2)

And another user request.  But...I can understand
	it now that I see it without.  They actually
	look quite nice this way.

Change-Id: Id0222140a41eec9e5cd27b769cf860ac62ede1c0
Frameworks: Fix possible ANR and navigation bar freeze

Big thanks to ralpheboyo which provided us the first time a usable
anr trace where we can see what the actual problem is.

The random ANR is caused due of to much work on the navigationBarCanMove
feature. We call way to often the provider value even though it is only
needed on initiliazing or on update of the value. Currently we call it on every
possible navigation bar change and this multiple times.

To fix it just call it on init and on contentobserver changes and pass
the new value to the navigation bar view and the search panel view

PS:
- remove another call
PS
- add one security check just to be sure
PS
- get one step further and put out the navigation ring config as well
  and reduce it to just one call.

Change-Id: Ica6116289d5bc50e9bedcd34b4b165062fa3468d
Frameworks: Port Lockscreen Targets, Shortcuts and more

First thanks to PA and CM which gave us partly code and some ideas.
Still some parts of the original implementation are/were buggy as well
we needed to ehance it.

Whatever the new Slim version is now ready and seems to be completly bug
free.

- Configurable lockscreen targets...on tablets 8 on phone either 5 or 8
- configurable lockscreen shortcuts only on phones...up to 5 shortcuts
- Centralazing some methods....using now then rounded corner on custom
  images systemwide...means on all other shorcut features we have
- multiDpi compatible
- new settings logic
- instance handling of all dialogs like we do on all other places
  way nicer this way
- tons of fixes

Change-Id: Ib3752204aa6876bd5b9d619c002df78d8e4bd109

This commit replaces CyanogenMods lockscreen targets with Slims version,
also adds custom colors for targets and text by @Jubakuba

orignal commits can be found here:
https://github.com/SlimRoms/frameworks_base/commit/334a61061efcb0e593ef580af7de8328e91341a1
https://github.com/SlimRoms/frameworks_base/commit/0c59b53f9a6a5beaddda5b2b6df88321f4e0b1f4