Upgrade Soroban env to latest patch

[Shaptic]

What

Bump dependencies to their latest versions and run cargo update.

Why

Self-explanatory.

[Shaptic]

@dmkozh looks like stellar/rs-soroban-env@5a28b69 was a breaking change to soroban-simulation: what's the appropriate resolution in this preflight call?

Or is it more correct to remove unstable-next-api from our toml?

---

Edit: Went with the second option, which changes the question: what should it be in the future when we're ready to use the next API?

[dmkozh]

was a breaking change to soroban-simulation

Yes, it's expected to be breaking, which is whyunstable-next-api guard is used. I'm surprised this feature is enabled by default in RPC. FWIW the particular change is done in order to allow addressing #344 in RPC.

I think it would make sense to remove this feature from RPC (as it has to be added intentionally), but it also makes sense to update to just 22.1.0.

[dmkozh]

Edit: Went with the second option, which changes the question: what should it be in the future when we're ready to use the next API?

I think a separate PR should be created for adaptation to the API changes. Basically the idea behind unstable-next-api is to clean it up on every major release and I think it makes sense for clients to remove it when bumping the major version of env. Then for the work in-between the releases it can be enabled in order to adopt the API changes without waiting for the major release.

[Shaptic]

Yep makes sense! We'll refactor for the new API as part of P23 work.