Fixes intersection functions (uint64, int64, []byte)

[farazdagi]

What type of PR is this?

Bug fix

What does this PR do? Why is it needed?

• Fixes issue with intersection functions, when argument list has more than 2 slices (issue is reported by audit team)

Which issues(s) does this PR fix?

Fixes #6029

Other notes for review

• This is an alternative PR to the one that has been created by Terence: Fix intersection functions #6050
• Terence's PR was blocked by what seemed to be issues in init-sync fetcher tests. The issue proved to be not in tests, but in how intersection was implemented: it modified passed in argument (the first slice), which was unexpected. While debugging the issue, I came up with this alternative implementation.
• This PR uses different implementation (still the one based on map - so efficiency is the same), which doesn't require modification of function argument. Also, I believe that proposed implementation is easier to reason about and more generic (so, should we want to use reflection - the very same code can be used for int64/uint64 and []byte - in previous implementation []byte has somewhat different code).
• More test cases has been checked
• Proposed action: either cherry-pick from this PR, or merge this one and close the original Fix intersection functions #6050.

[terencechain]

This looks good to me. Thank you for fixing this.
Happy to close the original one