clients/stellarcore: Add support for Core's new HTTP endpoints

[Shaptic]

Protocol 23: Core Endpoints

Epics: #5433, stellar/stellar-rpc#267

---

Stellar Core will have one new high-performance HTTP endpoint as part of their v22 in stellar/stellar-core#4350 which is supported as part of #5428. It will have three more in v23. We need to support them. The endpoint schemas are defined in this document and are replicated here (please check the document to ensure the following schemas are not outdated).

Request format

Each endpoint needs to be implemented into the stellarcore client as its described here. The format for every endpoint is the same POST request:

ledgerSeq=N&key=base64&key=base64...

Here, ledgerSeq is an optional uint32 number and each key is a base64-encoded xdr.LedgerKey. If the ledgerSeq is not available on the given instance, a 404 will be returned.

Response formats

Protocol 23: /getledgerentry

JSON response (as a TypeScript interface):

interface Response {
  ledger: number; // uint32
  entries: {
    e: string; // base64-encoded xdr.LedgerEntry or xdr.LedgerKey (if state == new)
    state: "live" | "new" | "archived" | "evicted"
  }[]

Note that this is REPLACING the existing endpoint, meaning we need to ensure that all code paths that use the current variant of the endpoint are updated correctly.

---

Protocol 24: Core Endpoints

The details are omitted here so they can be moved to a new issue when appropriate, since the endpoint schemas might change.

Request format

Each endpoint needs to be implemented into the stellarcore client as its described here. The format for every endpoint is the same POST request:

ledgerSeq=N&key=base64&key=base64...

Here, ledgerSeq is an optional uint32 number and each key is a base64-encoded xdr.LedgerKey. If the ledgerSeq is not available on the given instance, a 404 will be returned.

Protocol 24: /getinvocationproof

JSON response (as a TypeScript interface):

interface Response {
  ledger: number; // uint32
  proof?: string; // base64-encoded xdr.ArchivalProof
}

Note that if a proof is not required for any of the given entries, proof will be omitted.

Protocol 24: /getrestorationproof

JSON response (as a TypeScript interface):

interface Response {
  ledger: number; // uint32
  proof?: string; // base64-encoded xdr.ArchivalProof
}

Note that if a proof is not required for any of the given entries, proof will be omitted.

Notes

Core does not have a build ready with the Protocol 24 endpoints so they cannot be tested end-to-end.