Can't accept owned touch that has ended.

frame lib fails to forward the accept/reject command to xserver for an owned touch if it has already ended.

[Test Case]
Steps to reproduce the issue:
  1 - touch 1 begins and gets ownership
  2 - touch 1 ends
  3 - touch 2 begins and gets ownership
  4 - frame client accepts touch 1

An example of when this happens in normal usage is performing a three-touch tap on a touchscreen in unity where the first touch to hit the screen is over a menu item that opens a drop-down menu.

Expected outcome:
  Frame lib accepts the touch on the XInput backend. All further input events continue as normal.

Actual outcome:
  Nothing happens. Frame lib never accepts the touch. This causes the touchscreen to behave as though it has "locked up". Touches no longer cause emulated button press/release events, so it is hard to interact with the desktop.

[Regression Potential]
Small. Look for issues when using unity gestures on a trackpad or when using a touchscreen for any type of interactions in unity.

The actual code change involves removing logic that waits for a touch to end before it is accepted or rejected. This was required in the initial XInput multitouch protocol, but because unnecessary upon protocol finalization. Now, frame simply forwards accept and reject when they occur. This simplifies the code considerably.

A new regression test case has been added for this issue. All previous functional and regression test cases continue to pass.