horizon/ingest: Fix ingesting failed path payment operations

txnbuild: support protocol 12 (stellar#1817)

* fix: type definition should be alias declaration

* examples for new operations

* reverse aliasing for clarity

* apply suggestion

Co-Authored-By: Leigh McCulloch <[email protected]>

* apply suggestion

Co-Authored-By: Leigh McCulloch <[email protected]>

all: Upgrade to protocol v12 (stellar#1776)

This commit updates Go monorepo to support Stellar Protocol v12. The new
version changes some XDR types and adds a new `PathPaymentStrictSend`
operation (see: CAP-24).

Below are per package changes added to support v12.

* XDR Go definitions have been regenerated using `xdrgen`.
* Added `PathPaymentStrictSendResult.DestAmount()` helper method.

Because this package is no longer supported the only changes are type
name changes that allow the package to be compiled. No support for the
new `PathPaymentStrictSend` operation.

* Added a new `PathPaymentStrictSend` response to operation responses.
* Added new error codes connected to `PathPaymentStrictSend` operation
in `POST /transactions`.
* Changed `/payments` to include `path_payment_strict_send` operations.
* Updated `history_trades` table schema to allow amounts equal `0` (to
support cases where `ClaimOfferAtom` contains `amountSold = 0` and
`amountBought != 0`).
* Updated `ingest` package to support ingesting operations, effects and
trades that result from `path_payment_strict_send` operations.

Support for `PathPaymentStrictSend` in auth endpoint.

Added support `PathPaymentStrictSend` support. Check next section for
more information.

* Even though new operation has been implemented in Horizon's `ingest`
package it has not been tested yet! New test scenarios are required but
building them requires changes to `scc` (and `scc` requires changes to
ruby SDK).
* `PathPaymentStrictSend` has been added to `txnbuild` but there's an
ongoing discussion whether we should release it now or after v12
upgrade. See: stellar#1773.
* Horizon schema change skips one number (`21` vs `20`) as `20` was used
in Horizon 0.21.0 and it's not been merged into master yet.

Remove EXTENSIONS from initial schema

Horizon 0.21.0 CHANGELOG and docs (stellar#1770)

Horizon 0.21.0 CHANGELOG and docs (stellar#1770)

support/historyarchive: Fix error reporting (stellar#1648)

After deploying `release-horizon-v0.20.1` branch to staging server it
stopped processing ledger entries after around 300k entries with an
error:
```
Read wrong number of bytes from XDR
```
returned from `XdrStream.ReadOne`. First, I changed the code to return
`err` values before proceeding to the next checks. This reveal the real
error:
```
stream error: stream ID 311; PROTOCOL_ERROR
```
I couldn't find any information online about this but I suspect this is
happening because of the idle timeout. In `SingleLedgerStateReader` we
preload entries for a better performance (smaller round-trip time) when
getting temporary data from `TempSet`. When entries are being processed
the connection stays idle. The second fix (actually: quickfix) was
decreasing `preloadedEntries` to `20000` what makes a delay between
streaming batches shorter. However it's not a permanent fix. The issue
is tracked in stellar#1649.

support/historyarchive: Fix error reporting (stellar#1648)

After deploying `release-horizon-v0.20.1` branch to staging server it
stopped processing ledger entries after around 300k entries with an
error:
```
Read wrong number of bytes from XDR
```
returned from `XdrStream.ReadOne`. First, I changed the code to return
`err` values before proceeding to the next checks. This reveal the real
error:
```
stream error: stream ID 311; PROTOCOL_ERROR
```
I couldn't find any information online about this but I suspect this is
happening because of the idle timeout. In `SingleLedgerStateReader` we
preload entries for a better performance (smaller round-trip time) when
getting temporary data from `TempSet`. When entries are being processed
the connection stays idle. The second fix (actually: quickfix) was
decreasing `preloadedEntries` to `20000` what makes a delay between
streaming batches shorter. However it's not a permanent fix. The issue
is tracked in stellar#1649.

Pre-release updates to Horizon 0.20.0 (stellar#1632)

* Updates CHANGELOG with old deprecated, postponed fields.
* Adds `Action Needed` tag for deprecated fields.
* Changes `expingest.CurrentVersion` to `2` (no need to increment it
  more than once in a single release).

get next and prev trade aggregations (stellar#1581)