Provide a simple mechanism for users to increase the initial Soroban settings limits

[sisuresh]

The initial Soroban settings are low so when we launch on testnet, they'll be in what we call "safe mode". The issue with this is that users that are testing on a fresh local network will have issues with hitting the low max values. We should provide a simple way to increase these value.

[MonsieurNicolas]

This is probably related to #3822 and/or #3863 ?

[sisuresh]

Yeah but the current mechanisms are too complex for users to rely on. I think for now the simplest this is to provide a boolean config flag called TESTING_HIGH_SOROBAN_LIMITS and just set values to something we don't expect users to hit.

[MonsieurNicolas]

In which scenario would we use this? In testnet we will not use this: we have to follow production procedures

[sisuresh]

This would be used for standalone quickstart and platform e2e tests.

[MonsieurNicolas]

As a short term band-aid this could be enough if you're trying to unblock e2e testing.

That being said, in e2e tests and standalone, I imagine that some tests will want to use values that are in production?

In the linked issue I thought people would prepare a few "profiles" that match whatever scenario people expect to test.

Similarly, even in core supercluster missions, we'll need "high tps" profiles that allow to properly flood transactions.

[sisuresh]

Yeah this is a quick fix. We need to add someway for users to set settings to our different "phases".