fix: remove the use of detail as this is a synthetic event value and will not be compatible with React 17

[janechu]

Description

Removed the check using detail and resolve whether a click is a single or double click using only setTimeout.

Motivation & context

The use of the synthetic events detail would occasionally result in console logs being generated from React. Due to this also being removed in React 17 the double click detection is remediated to work solely from setTimeout.

Issue type checklist

• Chore: A change that does not impact distributed packages.
• Bug fix: A change that fixes an issue, link to the issue above.
• New feature: A change that adds functionality.

Is this a breaking change?

• This change causes current functionality to break.

Adding or modifying component(s) in @microsoft/fast-components checklist

• I have added a new component
• I have modified an existing component
• I have updated the definition file
• I have updated the configuration file

Process & policy checklist

• I have added tests for my changes.
• I have tested my changes.
• I have updated the project documentation to reflect my changes.
• I have read the CONTRIBUTING documentation and followed the standards for this project.

[EisenbergEffect]

Possibly a different approach: https://developer.mozilla.org/en-US/docs/Web/API/Element/dblclick_event

[janechu]

@EisenbergEffect unfortunately I have an action for a single click as well as a double click. For React (not sure about native events), it will fire the double click once and the single click twice if a double click is used.

[codeclimate]

Code Climate has analyzed commit caaac97 and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 10.0% (50% is the threshold).

This pull request will bring the total coverage in the repository to 85.2% (0.0% change).

View more on Code Climate.