fix(effects-ng): properly manage multiple effects with same class and function names

[EricPoul]

PR Checklist

Please check if your PR fulfills the following requirements:

• [x] The commit message follows our guidelines: https://github.com/ngneat/effects/blob/master/CONTRIBUTING.md#commit
• [x] Tests for the changes have been added (for bug fixes / features)
• [ ] Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: https://github.com/ngneat/effects/issues/60

What is the new behavior?

Does this PR introduce a breaking change?

[x] Yes
[ ] No

Other information

[stackblitz[bot]]

Run & review this pull request in StackBlitz Codeflow.

[EricPoul]

@NetanelBasal, I change the logic a little. Now I check prototypes of the instances to verify if instances are created by the same class or just instances share the same class name.