Automatically decode XDR for getLedgerEntries and friends

[Shaptic]

What

We have the following breaking schema change in the top-level response:

-entries?: LedgerEntryResult[];
+entries: LedgerEntryResult[];

and in each entry:

-key: string;
-xdr: string;
+key: xdr.LedgerKey;
+val: xdr.LedgerEntryData;

More specificially,

• entries is now guaranteed to exist, but it may be empty
• entries[i].key is an instance of xdr.LedgerKey
• the entries[i].xdr field is now val, instead
• entries[i].val is an instance of xdr.LedgerEntryData

If users want to continue to use the raw RPC response, there is still a Server._getLedgerEntries method.

Some helpers from previous PRs have been moved around into a new src/parsers.ts, also.

Why

Better UX, see #128.

[sreuland]

once it's available in the wild, nothing prevents clients from using in their production side code, should comment just be removed or not exported?

[Shaptic]

I can't avoid exporting because it would mean it isn't available for browser testing, unfortunately :( you're right that nothing is stopping people from using it if they want. I added a comment to that effect in 47e445e.

[sreuland]

nice work!

[socket-security]

New and updated dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
eslint	8.51.0	filesystem, environment	+35	6.15 MB
@babel/preset-env	7.22.20	environment	+125	13.8 MB	nicolo-ribaudo
@babel/cli	7.23.0	eval, filesystem	+33	11 MB	nicolo-ribaudo
@babel/core	7.23.0	filesystem, environment	+28	9.97 MB	nicolo-ribaudo
chai	4.3.10	environment	+7	921 kB	keithamus
sinon	16.1.0	environment	+12	7.18 MB	fatso83
@types/mocha	10.0.1...10.0.2	None	+0/-0	96.3 kB	types
@types/sinon	10.0.16...10.0.18	None	+1/-1	94.2 kB	types
@babel/preset-typescript	7.22.15...7.23.0	None	+32/-8	10.1 MB	nicolo-ribaudo
@typescript-eslint/parser	6.7.0...6.7.4	None	+41/-1	7.86 MB	jameshenry
@types/node	20.6.0...20.8.2	None	+0/-0	3.92 MB	types
axios	1.5.0...1.5.1	None	+1/-1	1.8 MB	jasonsaayman