Make senders be the same for different gesture EventArgs

[jknaudt21]

Description

This is a follow up issue to this discussion: #16802

Long story short, depending on what type of gesture event you're receiving, for example, TapEventArgs or DragEventArgs, the sender of these events may vary. In some cases this is the element itself. In others, its the GestureRecognizer.

This makes handling these events not the most pleasant experience since it lacks consistency. This proposal aims to centralize the behavior, preferably such that the sender is the element itself and not a gesture recognizer.

Public API Changes

The main change would live in the GestureRecognizers. Its just a matter of determining what to send when we emit the event.

This proposal was roughly implemented (and reverted) here: 3007fed#diff-45a3ddde1521a9a52178c9992e1458073808a9deb7e67f290347a8b87cdf8b4bL94-L116

Intended Use-Case

Using GestureRecognizers should be a uniform standard experience. Users shouldn't need to worry about if the sender differs.

[ghost]

We've added this issue to our backlog, and we will work to address it as time and resources allow. If you have any additional information or questions about this issue, please leave a comment. For additional info about issue management, please read our Triage Process.