Do not always call setIsConnectedToProvisioningNetwork(false)

Previously I was calling setIsConnectedToProvisioningNetwork(false) always,
but all MDST's receive every broadcast. Thus we could over write an MDST's
mNetworkInfo.mIsConnectedToProvisioningNetwork to false, unless the MDST
that was set to true was last, i.e the code was order dependent.

If the provisioning networks value was false instead of true
when handleMobileProvisioningAction was called we wouldn't invoke
mdst.enableMobileProvisioning because network info would be null.

Thus the provisioning network would never transition to CONNECTED and
a default route wouldn't get setup and the browser couldn't access the
website.

Now setIsConnectedToProvisioningNetwork is only set to false when the
apnType matches and we won't indiscriminately change it and are not
order dependent.

Bug: 10853805
Change-Id: I68a4f9bdf5dc18d90f4cdef7a60811f57be67261
SystemUI: SK translations

Change-Id: I2a3155f4300a4eedf55f0b0d204185052af90d62
Frameworks_base: Add AF Translations

Change-Id: Ib03427c8d753c7e3412063fc1312a4c2c886ef7a
Merge "SystemUI: SK translations" into cm-10.2
core: SK translations

Change-Id: Id9ec746c867f6379f05913e2a9f02c5ce5bfa7cc
SystemUI: zh-rTW translations

Change-Id: I94bd89027e97b6dcc48d29181a8145452bb96f4c
Fix unresponsive home key after waking device with a long press

With the lockscreen disabled mHomeConsumed would not be properly set back to
false upon releasing the key, causing a subsequent press to perform no action.

Change-Id: I38eeba5850c2f0474cc4cca82a9dcbf17afa4665
Merge "Frameworks_base: Add AF Translations" into cm-10.2
Merge tag 'android-4.3.1_r1' into HEAD

Android 4.3.1 Release 1
Merge "Fix unresponsive home key after waking device with a long press" into cm-10.2
Merge remote-tracking branch 'upstream/cm-10.2' into cm-10.2