soroban-rpc: enforce network limits during preflight

[MonsieurNicolas]

Not all limits are implemented right now.

This issue tracks both adding the missing ones enforced at validation/apply time, and enforcing them during preflight.

• int64 txMaxSizeBytes; // maximum size an xdr encoded transaction can be (also enforced by the tx endpoint)
• int64 txMaxGas; // maximum gas per transaction
• uint32 txMaxReadLedgerEntries; // maximum number of ledger entry read operations per transaction (footprint)
• int64 txMaxReadBytes; // maximum number of bytes that can be read per transaction
• uint32 txMaxWriteLedgerEntries; // maximum number of ledger entry write operations per transaction (footprint)
• int64 txMaxWriteBytes; // maximum number of bytes that can be written per transaction
• uint32 txMaxExtendedDataSizeBytes; // maximum size of extended data produced by a transaction (this
• int64 txMaxResultSizeBytes; // maximum size of a transaction result (gets folded into txMaxExtendedDataSizeBytes if we replace this by the hash in history archives)

I grabbed most of this list from https://github.com/stellar/stellar-protocol/blob/master/core/cap-0046-07.md but there could be more.

[MonsieurNicolas]

@sisuresh FYI

[jayz22]

Updated fee-related network limits:

    // Maximum instructions per transaction
    int64 txMaxInstructions;

    // Memory limit per transaction.
    uint32 txMemoryLimit;

    // Maximum number of ledger entry read operations per transaction
    uint32 txMaxReadLedgerEntries;

    // Maximum number of bytes that can be read per transaction
    uint32 txMaxReadBytes;

    // Maximum number of ledger entry write operations per transaction
    uint32 txMaxWriteLedgerEntries;

    // Maximum number of bytes that can be written per transaction
    uint32 txMaxWriteBytes;

    // Maximum size of extended meta data (mostly from events) produced by a transaction
    uint32 txMaxExtendedMetaDataSizeBytes;

(see the google sheet for their relation to the fee calculation)

Other limits that may also need to be validated:

    // Maximum size in bytes for a transaction
    uint32 txMaxSizeBytes;

    // Maximum allowed size of contract code in bytes (relevant for install install contract and update contract code)
    uint32 contractMaxSizeBytes;

    // Maximum contract data key and entry size 
    uint32 contractDataKeySizeBytes{};
    uint32 contractDataEntrySizeBytes{};

These value are all specified ConfigSettingEntry from the network and preflight needs the additional logic to compare the simulateTransaction output against these limits (and provide the info to the user).

(Discussed offline with @tsachiherman and @dmkozh )

[sisuresh]

The limits have already been enforced in core, so I transferred the issue over here for the pending rpc work.