power: smb5: Avoid potential votable deadlock issue

There exists a possible deadlock scenario whenever fcc_votable
and usb_icl_change votable rerun happens simultaneously since in
the fcc votable path, following locks can be acquired in sequence:
pl_disable lock -> fv_votable lock -> usb_icl_change lock, and in
the usb_icl_change votable, pl_disable lock needs to be acquired.
So based on race condition, there exists the possibility of
deadlock if pl_disable lock is acquired by FCC votable rerun first
but simulaneously, usb_icl votable is also locked on another thread.
Avoid this situation by preventing acquisition of usb_icl votable
lock in the fcc_rerun election path.

Change-Id: Icafad5fdade30ef15d581fe5afb3427667a4a922
Signed-off-by: Umang Agrawal <uagrawal@codeaurora.org>