Fix lost reactivity when using deps

[CaptainN]

This attempts to fix various lost reactivity reports, as well as some trouble with a particular "Maximum update depth exceeded" error, coming from (possibly) constantly updating deps interaction with useEffect, in two ways:

• Adds guards against containing computations effecting the enclosed computation in useEffect.
• Adds a system to keep the reference to reactiveFn always up to date with the latest render.

All tests are passing, but I'd like to see if we can work out a test to confirm the reported error.

313

[CaptainN]

We have at least one validation that the approach in this PR fixes the reported issue. @filipenevola Due to the severity of this bug, I don't think we should wait for a test - we should release a new version 2.2.2.

https://github.com/meteor/react-packages/issues/313#issuecomment-769018365

[make-github-pseudonymous-again]

Repeating what I said in #306:

• @CaptainN I confirm using deps in useTracker works as expected in my project with react-meteor-data@2.2.2.
• Could a hook waterfall be used as regression test for this fix?