Add logs to trace no window touched and cancel event

To clarify some unresponsive touch problems, we have to know if the
event has really sent from firmware and some window could be touched
or it's dropped because of cancel.

- Add the explicit log where we did not really find a touched window.
- Add input_cacnel event log to identify the reason.

Test: atest inputflinger_tests
Bug: 201647070
Bug: 200837970
Change-Id: I17b1de6c96ddc11d2ca2efd00e30e00847b98406