persist the blur event so clients can use it

[triptate]

This fixes a bug where the event that is passed to the onBlur prop will be nullified because the code is executed asynchronously using a timeout. I expect there's a good reason why the timeout is necessary; however, if it were not necessary, then removing the timeout would be a simpler and more efficient solution to this problem since event.persist() creates a copy of the event.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/react-component/mentions/lr8wg2lbx
✅ Preview: https://mentions-git-fork-pegulabs-persist-blur.react-component.now.sh

[codecov]

Codecov Report

Merging #24 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #24   +/-   ##
=======================================
  Coverage   99.13%   99.13%           
=======================================
  Files           6        6           
  Lines         230      232    +2     
  Branches       52       53    +1     
=======================================
+ Hits          228      230    +2     
  Misses          2        2           

Impacted Files	Coverage Δ
src/Mentions.tsx	99.30% <100.00%> (+<0.01%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e613351...079e17d. Read the comment docs.

[triptate]

@afc163 this one didn't seem to need a test case; however, an alternative strategy would be to add a prop that allows the client to indicate if they would like the event to be persisted in this case (e.g. persistOnBlur). in this case, this code would only run conditionally if the prop is included, and it would need a test case as well. let me know if you'd like me to rewrite this using that approach.