Fix Raft scenarios with dependency on dispatch order

[eddyashton]

As noted here:

#6588 (comment)

These 2 raft scenarios (reconfig_01_23 and reconfig_01_el0_23) are failing when built with libstdc++ (rather than libcxx), as the dispatch_all steps produce a different iteration order. In situations where multiple nodes could become primary, this results in a different node succeeding than was asserted.

I believe the correct fix is to remove the assertion, we can only say that a node has become primary, and back that up with stronger assertions later to ensure both nodes have fully caught up with commit progress.

Closes #6718

[maxtropets]

@eddyashton Could you please also remove raft_scenario filter from ci.yml for Azure Linux test run?