Track the share_click share_close differently if blocked

[tttp]

We track two events: when the share window is open, and when it's closed

However, on some social media, their site is set up so the close window is always triggered, even if it's not the case

It's kind of creating noise and twice as many events as needed

proposal:

instead of directly record the share_click,

• put it in a timer (ie delay the recording by 500ms or 1s)
• if the close event is received before the timer is executed, cancel it
  and we should probably change the share_close by share, easier to communicate

that's it ;)

so we will have less noise and only see the real cases when the click and the close are different (eg using share native)