build(connector-stellar): add a run soroban transaction endpoint

[fazzatti]

• Add a run soroban transaction endpoint to the Stellar Connector plugin.

Remarks:

The runSorobanTransaction endpoint can be used to make smart contract invocations on the Soroban platform. The endpoint accepts a flag called readOnly to indicate when the transaction should not alter ledger state. When true, the transaction will only be simulated based on the current ledger state and provide an up-to-date output without registering the transaction to the ledger, ensuring no fees are consumed. When false, the transaction will be executed and registered to the ledger even if it doesn't alter the ledger state, incurring fees as usual.

More details can be found in the README.md file under the connector root directory.

Closes #3238

Pull Request Requirements

• Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
• Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
• Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

• Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
• Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

[petermetz]

@fazatti ^^ Please see comments above!

[fazzatti]

Hi @petermetz !

It took me a while to make all the adjustments and add the Rust project of the demo contract, but I've managed to complete it. Would you please have a look and review it whenever you are available?

[petermetz]

@fazzatti Looking good to me, thank you again for the contribution and the updates! :-)

[outSH]

Thanks, looks great ;) I've added a small nitpick but it's optional

[outSH]

Oh sorry, reverting approval, I've forgot we've merged a change in openapi definitions yesterday (4a9ed0a)

Please apply the changes you've made in openapi.json to openapi.tpl.json instead (it's in the same folder), then run the npm run codegen - this will create the final openapi.json. In general, all changes should be made to the tpl.json file from now on :)

[fazzatti]

Hi @outSH !
Thank you so much for the comments, I made the suggested changes and hope everything is ok now!

[outSH]

LGTM, thank you!

[petermetz]

@fazzatti Please resolve the merge conflict in the opanpi.tpl.json file! Let me know if you need any help! See my earlier posts on what the new openapi.tpl.json file is if you aren't sure!

[fazzatti]

@petermetz thank you so much! I took a beating from this last update 🤣
While trying to fix the conflict, I ended up causing a big mess in my branch, but after some probing around and digging deeper, I think I've managed to correct everything. 🙏

Please let me know if you notice anything I might've missed, or that requires any additional steps.

[petermetz]

@fazzatti No worries, I'm glad it got figured out in the end :-) Please squash the commits together though!

[fazzatti]

@fazzatti No worries, I'm glad it got figured out in the end :-) Please squash the commits together though!

Sorry about that, I completely forgot about not using the update branch button 🤦

[petermetz]

@fazzatti No worries, thank you again for the contribution(s)! :-)