mospy sentinel chain

[Tkd-Alex]

Hello Felix, first of all thank for your awesome work! ❤️
We are developing a sentinel_sdk in python and I had to add the sentinel_protobuf inside mospy.

Currently the sentinel_protobuf is maintained by @MathNodes. I saw that 2 weeks ago you accept the PR ctrl-Felix/cosmospy-protobuf#14, but the pypi release is Nov 27, 2023 (without the sentinel_protobuf).

I had to change the requirements from cosmospy_protobuf to sentinel_protobuf.
Now we have two options:

1. Continue to maintain separate the protobuf and mospy package, obviously will be create a pypi package sentinel_mospy
2. Pubblish on pypi the latest version of cosmospy_protobuf (that include also sentinel) and the release an update also for mospy (this PR - with the requirements.txt rollbacked to cosmospy_protobuf)

What do you think?

The PR include also a GetTx method, out of sentinel/chain related scope.

[ctrl-Felix]

Thanks for your contribution :)

I've seen the sentinel protobufs and I am very happy to see that there's a community contributed protobuf package!

Regarding the integration into mospy. I think there's not specific need for a sentinel_mospy package, at least not on my end. There's no osmosis_mospy package either. And you can already use sentinel with the current mospy package. Because you can pass "sentinel_protobuf" when creating the Account/Transaction instance which will work. The dict with the protobuf names is just to add an alias. But I think it's a good idea to add sentinel to these too.

Regarding the get Tx. I want to improve the clients anyways but to keep them both consistent I'd prefer to make a new pr/branch with a proper client update.

[Tkd-Alex]

as you request I've moved the GetTx in to another pull request (#25), I've rollbacked the requirements.txt