Update the Protocol 20 community SDK issues with new XDR/API changes

[Shaptic]

Once the XDR and API are stabilized, we will need to inform the community SDK maintainers about the changes.

The CLI script can add comments rather than open new issues, but a new issue is better given that many SDK repos have already closed the Protocol 20 issues (e.g. Soneso/stellar_flutter_sdk#73).

Summary of Changes

XDR

The XDR needs to be updated to stellar/stellar-xdr@6a620d1. This includes a non-trivial list of breaking changes (mostly renames):

• The BumpFootprintExpirationOp is now ExtendFootprintTTLOp and its ledgersToExpire field is now named extendTo, but it serves the same purpose.
• ContractExecutable.contractExecutableToken is now contractExecutableStellarAsset
• SorobanTransactionData.refundableFee is now resourceFee
• This new fee encompasses the entirety of the Soroban-related resource fees. Note that this is distinct from the "network-inclusion" fee that you would set on your transaction
• see Upgrade XDR to the final, stable testnet version. js-stellar-base#704 for an example migration

RPC

• The getEvents RPC endpoint structure has changed:
  • value: { xdr: string } is now just value: string (Flatten the getEvents response structure #1015)
  • contractId will always be a contract strkey (C... format) if present (The contract ID returned by getEvents should be a strkey #1007)
• The getLedgerEntries RPC endpoint now includes expiration info (soroban-rpc: Better state expiration support for getLedgerEntry #1010):
  • expirationLedgerSeq is a string-ified uint32 present if the requested entries have expiration

[2opremio]

I would explicitly mention the XDR symbol renames, and the operation BumpFootprintExpiration->ExtendFootpintTTL rename in particular

Otherwise it LGTM!