Fix DoubleTapped on touch

[Takoooooo]

Before this PR DoubleTapped event cant be triggered by touch input. Now it should work correctly.
Other frameworks like WPF\WinForms doesn't seem to count more than 3\4 clicks but I think there could be some use-cases for that so our implementation just basically counts clicks without any limitations. I don't have any devices with Touch so I can't test it, please test it by yourself. If more tests are needed I can add some. Click counting logic is copy-pasted(mostly) from MouseDevice but I don't think I can refactor it or improve in any way.
Also fixes DoubleTapped to be raised even if you click 4,6,8..etc times in a row, it matches UWP behaviour.
Also fixes Tapped. Now it wouldn't be raised twice when you click twice, Tapped would be raised once and DoubleTapped once,matches UWP behaviour.
Note:
On this line I hardcoded those values because we don't have separate settings for touch and it is really hard to hit into the size of the square declared for the mouse with touch. It is temporal change.

Checklist

• Added unit tests (if possible)?

Obsoletions / Deprecations

ClickCount is not Obsolete anymore.

Fixed issues

Closes #5412
Closes #6949

[Takoooooo]

I wonder where those warnings come from and how can I see them on Windows?

[kekekeks]

That's a global variable. We usually try to avoid those

[robloo]

Device and input state information must usually be maintained and managed centrally. It might help to suggest an alternative. Otherwise, I expect to see things like this myself.

[kekekeks]

The app might run on 2 independent touch screens. Or even on 1 touch screen with 2 windows on it. Because of such global variables we'll misinterpret tap sequences caused by the user tapping on those windows sequentially.

[Takoooooo]

We decided to temporarily leave it as is

[robloo]

Nothing is more permanent than temporary :) I would comment in the code that it should change in the future and why.

[kekekeks]

Nothing is more permanent than temporary

Yes, the original static variable in that file dates back to 2016 when DoubleTapped event was introduced. So we aren't introducing any new problems.

[grokys]

I'm getting an intermittent test failure in Tapped_Event_Is_Fired_With_Touch after this PR; the tests in TouchDeviceTests register services outside of the UnitTestApplication (meaning that those services are getting registered for all tests that are run in that test run) and Tapped_Event_Is_Fired_With_Touch doesn't register those services, so it will fail if ran before the others.

All service registrations for unit tests need to be done inside the using (UnitTestApplication.Start()) blocks in order to make sure they're cleaned up for when other tests run, and the registrations also need to be done in Tapped_Event_Is_Fired_With_Touch.