STOP Recovery: Removed OCI address with SCOM address in HWP error xml.

In PM Reset path, HWP tries to collect FFDC pertaining to PM complex.
For a GPE2 register, instead of using a SCOM address it was using
OCI address. Commit fixes the issue by updating the HWP error xml.

Key_Cronus_Test=PM_REGRESS

Change-Id: I2d4d6324742c91b23f31bd72f2d53c7ee8addfa1
CQ: SW447961
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/67284
Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com>
Tested-by: HWSV CI <hwsv-ci+hostboot@us.ibm.com>
Tested-by: Hostboot CI <hostboot-ci+hostboot@us.ibm.com>
Reviewed-by: RANGANATHPRASAD G. BRAHMASAMUDRA <prasadbgr@in.ibm.com>
Reviewed-by: Gregory S. Still <stillgs@us.ibm.com>
Reviewed-by: Jennifer A. Stofer <stofer@us.ibm.com>
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/67293
Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com>
Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com>
Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com>
Reviewed-by: Christian R. Geddes <crgeddes@us.ibm.com>

src/import/chips/p9/procedures/xml/error_info/p9_pm_registers.xml

@@ -630,7 +630,7 @@
     <scomRegister>PU_GPE1_GPEIVPR_SCOM</scomRegister>
     <scomRegister>PU_GPE2_GPEIVPR_SCOM</scomRegister>
     <scomRegister>PU_GPE3_GPEIVPR_SCOM</scomRegister>
-    <scomRegister>PU_GPE2_GPEDBG_OCI</scomRegister>
+    <scomRegister>PU_GPE2_GPEDBG_SCOM</scomRegister>
     <scomRegister>PU_GPE0_PPE_XIRAMDBG</scomRegister>
     <scomRegister>PU_GPE0_PPE_XIRAMEDR</scomRegister>
     <scomRegister>PU_GPE0_PPE_XIDBGPRO</scomRegister>