services/horizon/internal/ingest: Log tx meta when ingestion failures occur

[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

close #5257

Logs tx meta whenever there is an error encountered in any of the change processors. See below for an example log message:

time="2024-03-29T17:32:21.236Z" level=error msg="error processing change" change="Change{Type: LedgerEntryTypeAccount, Pre: AAAACgAAAAAAAAAAti4BUQwWdyedpy5t9JKtojIKzu3WM2ADd4b47X9SB1oAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=, Post: AAAACwAAAAAAAAAAti4BUQwWdyedpy5t9JKtojIKzu3WM2ADd4b47X9SB1oAAAAAAAAAyAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=}" error="transient error" pid=90088 sequence=1 service=ingest

Why

See #5257

Known limitations

[N/A]

[Shaptic]

nice!