init.qcom.rc: Remove /data/system/wpa_supplicant, fixes WiFi on upgrades

libhardware_legacy's wifi_connect_to_supplicant checks if (the symlink)
/data/system/wpa_supplicant exists, and if so, assumes it points to a
directory containing the wpa_supplicant control socket.  This is _not_ the
location of the wpa_supplicant control socket on d2/jf, and so, the symlink
should not exist.

CM 10.2's init.qcom.rc creates the /data/system/wpa_supplicant symlink,
with /data/misc/wifi/wpa_supplicant as its target.  However, it does not
create the target directory itself, so the wifi_connect_to_supplicant check
(correctly) fails.

CM 11.0 does create the /data/misc/wifi/wpa_supplicant directory, but not
the corresponding /data/system/wpa_supplicant symlink.  So the
wifi_connect_to_supplicant check also fails.  However, as the symlink
already exists on 10.2 upgrades, the check passes, resulting in
wpa_supplicant attempting to use the non-existant
/data/system/wpa_supplicant/wlan0 control socket.  Thus, the
/data/system/wpa_supplicant symlink needs to be removed to ensure that WiFi
on upgrade installs functions corectly.

Change-Id: I01c943cdb5e9e3b188a8a059f23f2beaf70e5ef7
Revert "jf: Enable sensor setrate on enable hack"

This reverts commit 2b10bdcfc27d47df9b86a73190fc814765a080d9.

Change-Id: Idc2bf67a25db398781483578450661a570e54432
Merge "init.qcom.rc: Remove /data/system/wpa_supplicant, fixes WiFi on upgrades" into cm-11.0
Merge remote-tracking branch 'upstream/cm-11.0' into cm-11.0