ingest: Update ingestion library and horizon to adapt to protocol 23 representation of evictions

[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 reviewed the changes in this PR and if I consider them worthwhile for being mentioned on release notes then I have updated the relevant CHANGELOG.md within the component folder structure. For example, if I changed horizon, then I updated (services/horizon/CHANGELOG.md. I add a new line item describing the change and reference to this PR. If I don't update a CHANGELOG, I acknowledge this PR's change may not be mentioned in future release notes.
• 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

CAP-62 and CAP-66 updates the LedgerCloseMeta xdr to no longer populate the evictedPersistentLedgerEntries field. Instead, both persistent and temporary ledger keys will be included in the evictedTemporaryLedgerKeys field which will be renamed to evictedKeys in protocol 23.

The ingestion library previously presented evictions of persistent ledger entries as a Change instance with the Reason set to LedgerEntryChangeReasonEviction. This allowed downstream consumers of a Change stream to handle evictions as if they were equivalent to ledger entry deletions. However, in protocol 23 we can no longer maintain this strategy because the full contents of the evicted ledger entry will not be present in the LedgerCloseMeta xdr. We will only have the ledger key for the evicted ledger entry.

This means that ledger entry evictions will need to be handled outside of Change stream processing by downstream services. The second commit of this PR fixes the asset stats processor in Horizon to adapt to this new reality where evictions no longer appear in the Change stream.

The asset stats processor can ignore evicted contract balance ledger entries because contract balance ledger entries are deleted from the horizon db immediately upon expiration. However, the asset stats processor still needs to ingest the stellar asset contract instance storage so that we can link stellar classic assets with their corresponding contract id. So when the stellar asset contract instance storage is evicted we also need to handle that event so we can remove the link between stellar classic asset and the stellar asset contract id.

Also fixes #5578

Known limitations

[N/A]

[Shaptic]

This looks good from a change perspective if I understand it correctly, but I don't feel great about reviewing the asset changes since I'm relatively unfamiliar with them.

Either way, though, integration tests will reveal issues once RPC gets tagged off, assuming we have some for SAC+eviction+asset stats?

[tamirms]

Either way, though, integration tests will reveal issues once RPC gets tagged off, assuming we have some for SAC+eviction+asset stats?

@Shaptic yeah, we have a issue to capture writing the protocol 23 eviction / restoration integration tests: #5613