services/horizon/internal/ingest/processors: Refactor participants processors to support new ingestion data flow

[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

Similar to #5004 , this PR refactors the ParticipantsProcessor so it conforms to the following interface:

type horizonTransactionProcessor interface {
	ProcessTransaction(xdr.LedgerCloseMeta, ingest.LedgerTransaction) error
	Commit(ctx context.Context, session db.SessionInterface) error
}

This PR also makes use of the loaders implemented in #5019 because the history participants tables have integer column ids which refer to rows in the history_accounts table.

Why

#4909

Known limitations

Several tests are failing because the ingestion framework still needs to be updated to support the new interface. All those tests will be fixed after all the processors have been migrated to the new data flow.

[sreuland]

cool, the new Builder and Loaders decluttered the processor quite a bit!

[Shaptic]

this is coming along so well, wow 👏 and the future-loader model fits like a glove