isl9241: set current limit after EFS2 sysjump
isl9241: set current limit after EFS2 sysjump

this fixes an issue where the charger current limit is not set as
early as intended due to EFS2 interactions.

when EFS2 is enabled, we sysjump to RW very early - before INIT_HOOKS
run. any code in INIT_HOOK functions that is predicated by
system_jumped_to_this_image() will either always run or never
run. this is not the intended behavior.

charger_chips_init() is called from INIT_HOOKS, and that's where we
call isl9241_init(). we now need to check system_jumped_late() instead
of system_jumped_to_this_image() to get the intended behavior.

BRANCH=none
BUG=b:159769490, chromium:1072743
TEST=isl9241_init now sets current limit to 512mA right after EFS2
	sysjump (verified with additional debug printfs)

Change-Id: I6de12d947ea9abb8e6db85dee0129a7053d0708c
Signed-off-by: Caveh Jalali <08e24a66aefda7a55ca7d73f8903e0fb16eec763@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2265303
Reviewed-by: Keith Short <f6d578f97033c25f1206cb57d52f358974c82954@chromium.org>
Reviewed-by: Daisuke Nojiri <fd5f93af191bf7e8f73ea71cc3c0f66b41b1dd49@chromium.org>
Commit-Queue: Keith Short <f6d578f97033c25f1206cb57d52f358974c82954@chromium.org>
Tested-by: Keith Short <f6d578f97033c25f1206cb57d52f358974c82954@chromium.org>

coreboot/chrome-ec,coreboot/chrome-ec,coreboot/chrome-ec,coreboot/chrome-ec,coreboot/chrome-ec,coreboot/chrome-ec