BREAKING CHANGE: add MakeCallTx, SignTx and BroadcastTxCommit in GnoNativeApi

[D4ryl00]

This PR adds MakeCallTx, SignTx and BroadcastTxCommit in GnoNativeApi. So the front can directly calls these methods now.
This PR also cleans the GnoNativeApi files, mostly by removing unnecessary await keywords.

BREAKING CHANGE: the gasWanted parameter (used in several gRPC message) is now a bigint instead of a number to keep the precision in the calling stack.

[jefft0]

These parameters should be the same as call. In call, gasWanted is a number and is converted to bigint.

[D4ryl00]

I asked me the question. The best would be to do a changing break and also convert gasWanted as a bigint in the call function. Otherwise, we will limit the front end to put big values.
What do you think?

[jefft0]

In the Go code, these are normal integers. I don't know why the buf generator makes them bigint. (Maybe to make sure it can hold 64 bits.) I think we should as Iuri what he thinks.

[D4ryl00]

They are int64 which is the equivalent of bigint in typescript.
https://github.com/gnolang/gnonative/blob/main/api/gnonativetypes/gnonativetypes.go#L251

[iuricmp]

Makes sense to keep as bigint because converting them to number could...

Be careful coercing values back and forth, however, as the precision of a BigInt value may be lost when it is coerced to a Number value

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt

[D4ryl00]

I added @iuricmp also to review the typescript part.

[jefft0]

Tested by doing make npm.pack and installing in dSocial. Tested with the following code.

      const tx = await gnonative.makeCallTx("gno.land/r/berty/social", "AddReaction", args, gasFee, BigInt(gasWanted));
      const signedTx = await gnonative.signTx(tx.txJson, address);
      for await (const response of await gnonative.broadcastTxCommit(signedTx.signedTxJson)) {
        const result = JSON.parse(JSON.stringify(response)).result;
      }

Approved pending resolving the question of bigint vs. number.

[iuricmp]

Makes sense to keep as bigint because converting them to number could...

Be careful coercing values back and forth, however, as the precision of a BigInt value may be lost when it is coerced to a Number value

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt

[github-actions]

🎉 This PR is included in version 3.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀