Decode reject reason at backend

[DOBEN]

Purpose

Some backends send transactions on-chain. Until now, failed transactions only had an error code (such as -1, -2, ...) associated with them. Since most transactions are triggered by input from users (which can be faulty), decoding the reject reason/error code into human-understandable errors is preferred.

The contract_client in the Rust SDK did not expose the returnValue of the failed transaction which is needed to decode error codes reliably. This PR updates the backends to use a new local Rust SDK with the required exposed functionality. Since the local Rust SDK is used now, the context in some of the Docker build pipelines had to be updated.

Related to Concordium/concordium-rust-sdk#199

This PR updates the sponsored_transaction_service in the track-and-trace dapp to use the new functionality from the Rust SDK. Other backends will be updated in follow-up PRs.

Changes

• Update the submodule link to the Rust SDK.
• Use local Rust SDK instead of some released/hardcoded Rust SDK versions.
• Update the context of the Docker build pipelines which depend now on the local Rust SDK.
• Decode the reject reason for a failed transaction during the dry-run at the sponsored_transaction_service backend in the track-and-trace dapp.

[soerenbf]

Otherwise, looks good to me 😄