rild: Don't use the clientId argument with non-qcom hardware

Other modems' implementations won't know how to deal with it, and
some are confirmed to simply reject the RIL_Init call.

If the hardware isn't qualcomm, just skip the whole multi-ril stuff
entirely

Change-Id: I132a4d7fc3d4532b2015f7e95863fac78889f833

rild: Weaken the RIL_setRilSocketName symbol

custom libril implementations won't have it, but its lack isn't
fatal outside of multi-SIM

Change-Id: If8312078921bb4ed756dcd86e17e85847638c155
Create UPSTREAMS
Revert "rild: Don't use the clientId argument with non-qcom hardware"

This reverts commit b0fa0e93ebff5e03ae9a755ea5d541fa3fbc5a85.
Merge remote-tracking branch 'upstream/cm-12.0' into cm-12.0
Revert "rild: Don't use the clientId argument with non-qcom hardware"

This reverts commit a55174e830914aa6009e80e80e69a1a8005e0a5b.
hardware_ril: fix bad samsung proprietary ril init

rild create and pass an additional parameter to RIL_init function.
This force RIL_init, in libsec-ril.so (samsung proprietary ril library),
to give a null pointer (RIL_init fails) and breaks completely RIL.
This should fix this problem. To make this effective it is necessary to
add BOARD_NEEDS_SEC_RIL_WORKAROUND := true in your BoardCommonConfig.mk

PS3: fix typo

Change-Id: I14e66315fa25aa1db05dbe9a03422c63a421205c