Fix trace bug for error path in rt_fwnotify

There was a small error that got missed in review. Had some parameters
swapped in trace statement so we were outputting type where it said
queue and outputting queue where it said type

Change-Id: I6a93f59c4a4328861b22bbcce14ed67e911a8fe1
Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/54000
Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com>
Reviewed-by: Roland Veloz <rveloz@us.ibm.com>
Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com>
Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com>
Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com>
Reviewed-by: Matt Derksen <mderkse1@us.ibm.com>
Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>

src/usr/util/runtime/rt_fwnotify.C

@@ -363,8 +363,8 @@ void firmware_notify( uint64_t i_len, void *i_data )
                 TRACFCOMP(g_trac_runtime, ERR_MRK"firmware_notify: "
                     "Unknown FSP message type:0x%.8X, "
                     "message queue id:0x%.8X, seqNum:%d ",
-                    l_hbrt_fw_msg->generic_msg.msgq,
                     l_hbrt_fw_msg->generic_msg.msgType,
+                    l_hbrt_fw_msg->generic_msg.msgq,
                     l_hbrt_fw_msg->generic_msg.seqnum);
 
                 // Pack user data 1 with message input type and