Ensure power-workarounds run before poweron target

The workarounds script does some unbinding and rebinding of the ucd
driver so ensure all of this is done before power is considered
officially on. Other services start after the power on target completes
and they depend on the ucd driver being bound and available.

Tested:
Verified on a system that was failing due to this issue now powers on

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I1f4a3c856689c44c1e0358d5bb3464676224ee73
diff --git a/meta-witherspoon/recipes-phosphor/chassis/power-workarounds/witherspoon/power-workarounds@.service b/meta-witherspoon/recipes-phosphor/chassis/power-workarounds/witherspoon/power-workarounds@.service
index 74d8e4b..3bd1287 100644
--- a/meta-witherspoon/recipes-phosphor/chassis/power-workarounds/witherspoon/power-workarounds@.service
+++ b/meta-witherspoon/recipes-phosphor/chassis/power-workarounds/witherspoon/power-workarounds@.service
@@ -3,6 +3,7 @@
 Wants=ir35221-on-unbind@%i.service
 After=ir35221-on-unbind@%i.service
 Before=avsbus-disable@%i.service
+Before=obmc-power-on@%i.target
 Conflicts=obmc-chassis-poweroff@%i.target
 ConditionPathExists=!/run/openbmc/chassis@%i-on