cheza: Execute the power-off sequence on S3S5
cheza: Execute the power-off sequence on S3S5

Move the power-off call from S0S3 to S3S5, such that the hooks are
triggered in an expected order.

The console command apreset and apshutdown still have some wrong
orders. Will be fixed later.

BRANCH=none
BUG=b:119050865
TEST=Tried the following cases:
 * Cold reset:
   $ dut-control cold_reset:on sleep:0.2 cold_reset:off
   Result: S3 -> S5S3 -> S3 -> S3S0 -> S0
 * Long power press to shutdown:
   $ dut-control pwr_button:press sleep:20 pwr_button:release
   Result: S0 8s-> S0S3 -> S3 -> S3S5 12s-> S5 10s-> S5G3 -> G3
 * Long power press to power-on but then shutdown:
   $ dut-control pwr_button:press sleep:20 pwr_button:release
   Result: G3 -> G3S5 -> S5 -> S5S3 8s-> S3S5 12s-> S5 10s-> S5G3 --> G3
 * Not-long power press to power-on:
   $ dut-control pwr_button:press sleep:5 pwr_button:release
   Result: G3 -> G3S5 -> S5 -> S5S3 5s-> S3 -> S3S0 -> S0
TEST=Verified the suspend and shutdown hooks are triggered properly.

Change-Id: I6350d1535f1c6374eacc710c1b3f0c6e25027d1f
Signed-off-by: Wai-Hong Tam <04b587fdf5845741a0c5a8b9cd59ca72d73ef8fc@google.com>
Reviewed-on: https://chromium-review.googlesource.com/1325172
Commit-Ready: ChromeOS CL Exonerator Bot <fa429e5907f00867f797423aea74327bb02c91b6@appspot.gserviceaccount.com>
Reviewed-by: Philip Chen <3ee404f9ef892bc3fda6e6a76e65843b5fa44db2@chromium.org>

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