Fix: crmd: match only executed down events

Before, if a downed node had more than one event that could make it down (e.g.
a remote node with a fence and a connection stop), the crmd could match an
action that hadn't yet been initiated, and thus abort the transition
unnecessarily.