Settings: init correctly LockPatternUtils on configuration changes

Steps to reproduce:
- go to security pattern choice
- turn the screen to landscape
- result: crash

LockPatternUtils instance was not passed trough to LockPatternView.
Hence the crash and NullPointerExcpetion.

Fix it with correct initiliaze LockPatternUtils.

Change-Id: I38b495030b2c454effc901854bdcabfcbc10219a
[2/2] Gestures Anywhere

Conflicts:
	AndroidManifest.xml
	res/values/pa_arrays.xml
	res/values/pa_dimens.xml
	res/values/pa_strings.xml
	res/xml/more_device_settings.xml
[2/2] Settings: Add ADB Paranoia mode

ADB Paranoia mode will reboot the device in the event of the following:
- The device is locked
- An ADB master device is connected
- ADB Paranoia mode is enabled in Development menu
Used in conjunction with device encryption, this should offer decent
protection against malicious adversaries with basic physical access to
your device. This will not help if your device has hardware level
exploits that can be used without rebooting the device, and without
connecting ADB.

Change-Id: Ia92141dc1eb5c1e337f325b860afe6ee11348e2f

Conflicts:
	res/values/custom_strings.xml
	src/com/android/settings/DevelopmentSettings.java
Re-organize AdditionalSettings

- Seperate category between Quick Settings and Statusbar.
- Remove QuickSettings category if the device is not a phone.
- Put custom system animation and listview animation into a new category
- Move gesture anywhere outside of interface settings
pa_strings.xml: "Battery level around unlock ring" intead of "Battery around unlock ring"
Merge remote-tracking branch 'upstream/kitkat-remix' into kitkat-remix