services/horizon: Add transaction set operation count to history_ledger.

[abuiles]

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

Extend ingestion to store the total number of operations in the transaction set and expose it in the ledger resource via tx_set_operation_count.

Why

This feature was requested in #1385 and it will help us assess the used capacity of a transaction set.

With this change we have now the total count of operations in the transaction set and the number of successful operations.

Fix #1385.

Known limitations

[TODO or N/A]

[bartekn]

Please update CHANGELOG.

[abuiles]

@bartekn done and updated the base branch to 1.5 release.