#3960 Improve Soroban reporting

[Anonymous]

Originally created by: marta-lokhova

It looks like stellar-core info endpoint and logging are missing some basic information about Soroban. This makes it harder to understand what's going on with the node and debug. We should:

• Update the info endpoint to include current Soroban network limits. If this gets too verbose (ideally info should be as compact as possible), we can put all limits behind a compact=false flag, and only expose max soroban tx set size (or create a new endpoint sorobaninfo instead).
• During upgrades, it would be helpful to log values the network upgraded to. Note that when the node is armed for an upgrade but hasn't performed it yet, node's status should reflect the new upgrade values as well.

[Anonymous]

Originally posted by: MonsieurNicolas

+1 on new endpoint for this

we should log network settings changes (even if it means dumping entire ledger entries) as this only occurs when applying ledgers

as far as "armed upgrades" -- aren't we already logging the argument of the upgrade that can be used with [#3964] ?