Refactor: fencing: avoid duplicate variable for notification type

xml_to_event() previously checked for both F_SUBTYPE and F_STONITH_OPERATION in
the notification XML. For client notifications these will always be the same,
so just use one. (F_SUBTYPE can be "broadcast" in peer messages, but that is
not relevant to this usage.)