Enable rolling counter and verification of req id for Explorer

Rather than using a constant value based on which command is being
sent to the OCMB, we will instead define an attribute that is set
by the platform in some unique way to differentiate this particular
command/response from all others going on.  This will allow the
code to catch bugs where commands erroneously are sent to the wrong
target for some reason.

Change-Id: I3162a8ac040d8487e9311f770a0466ee8500b415
RTC: 210371
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/83851
Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com>
Tested-by: PPE CI <ppe-ci+hostboot@us.ibm.com>
Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com>
Tested-by: Hostboot CI <hostboot-ci+hostboot@us.ibm.com>
Reviewed-by: STEPHEN GLANCY <sglancy@us.ibm.com>
Dev-Ready: STEPHEN GLANCY <sglancy@us.ibm.com>
Reviewed-by: ANDRE A MARIN <aamarin@us.ibm.com>
Reviewed-by: Matt K Light <mklight@us.ibm.com>
Reviewed-by: Jennifer A Stofer <stofer@us.ibm.com>
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/84632
Reviewed-by: RAJA DAS <rajadas2@in.ibm.com>

src/import/chips/ocmb/explorer/procedures/xml/error_info/mss_exp_errors.xml

@@ -460,6 +460,8 @@
     </description>
     <ffdc>RSP_ID</ffdc>
     <ffdc>ERROR_CODE</ffdc>
+    <ffdc>EXPECTED_REQID</ffdc>
+    <ffdc>ACTUAL_REQID</ffdc>
     <callout>
       <procedure>CODE</procedure>
       <priority>MEDIUM</priority>