inconsistent treatment of enabled rules

[tballmsft]

Creating a program with two actions on the same resource triggered by the same event (press button A) yields different results:

• for change page, show icon, show number, the first action runs, the second does not
• for variable update, the second action fires fi

For all such rules, we would like them to run in order on the page. If a later action is in direct conflict with earlier (like switch page or displaying on 5x5 screen), the later one takes precedence, interrupting the first. For variables, assignments are just done sequentially in order on page.