Ingestion fastbatch cbp

[urvisavla]

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

Use FastBatchInsertBuilder for writing to claimable_balances and claimable_balance_claimants tables. FastBatchInsertBuilder uses ‘COPY' to insert into the db which is faster than using 'INSERT'.

Why

#5086

Known limitations

[sreuland]

@urvisavla , per the branching strategy discussion, you intend to change merge target on this PR to ingestion-next? Wanted to let you know, I have two changes headed into the branch soon:

• merge integrating new loaders and builders into processors #5083, enables fast batch in ingestion.
• port latest master onto ingestion-next

after which, if you then merge this PR to ingestion-next, we can then take the branch into some performance testing cycles to see how it's looking with all in, does this sound ok?

[urvisavla]

@urvisavla , per the branching strategy discussion, you intend to change merge target on this PR to ingestion-next? Wanted to let you know, I have two changes headed into the branch soon:

• merge integrating new loaders and builders into processors #5083, enables fast batch in ingestion.
• port latest master onto ingestion-next

after which, if you then merge this PR to ingestion-next, we can then take the branch into some performance testing cycles to see how it's looking with all in, does this sound ok?

Thanks @sreuland. Yes, as discussed, I am waiting for #5083 to be merged before I rebase and send this PR for review. I have started reviewing the #5083 and have a few questions that we can discuss tomorrow.

Also, I can port the latest master to ingestion-next branch if you have not already started.