rearrange order of returns in button behavior to ensure consistency across interaction

Previously, the order of returns in on_touch_move and on_touch_up meant that multiple Behaviors that had touch logic were order of subclassing dependent. on_touch_down did not have this problem because its first check was to super(). I reordered the returns in the move and up behaviors to match the behavior in down. I'm not super experienced with heavy inheritance, but I don't think there are any changes in logic here other than the order of return in on_touch_move