services/horizon/internal/ingest/processors: Dedupe participants deterministically

[tamirms]

PR Checklist

PR Structure

• This PR has reasonably narrow scope (if not, break it down into smaller PRs).
• This PR avoids mixing refactoring changes with feature changes (split into two PRs
  otherwise).
• This PR's title starts with name of package that is most changed in the PR, ex.
  services/friendbot, or all or doc if the changes are broad or impact many
  packages.

Thoroughness

• This PR adds tests for the most critical parts of the new functionality or fixes.
• I've updated any docs (developer docs, .md
  files, etc... affected by this change). Take a look in the docs folder for a given service,
  like this one.

Release planning

• I've updated the relevant CHANGELOG (here for Horizon) if
  needed with deprecations, added features, breaking changes, and DB schema changes.
• I've decided if this PR requires a new major/minor version according to
  semver, or if it's mainly a patch change. The PR is targeted at the next
  release branch if it's not a patch change.

What

There are a few places in horizon's ingestion code where we extract unique elements (for example, account participants for an operation) using a map data structure. The problem with that approach is that traversing elements in a map in Go produces a random ordering. We want to make horizon's ingestion workflow completely deterministic so this commit uses sorting to extract unique elements instead.

Why

Having a deterministic ingestion workflow makes it easier to test the correctness of ingestion.

Known limitations

N / A