fix: correct MsgCall args field tag number in protobuf encoding

[jinoosss]

Summary

This PR fixes an incorrect protobuf field tag number in the MsgCall message encoding. The args field was being encoded with tag number 42 instead of the correct tag number 50 that corresponds to field number 6 in the protobuf schema.

Problem

The generated TypeScript code had an incorrect wire format tag number for the MsgCall.args field:

• Incorrect: writer.uint32(42).string(v!)
• Correct: writer.uint32(50).string(v!)

This mismatch between the protobuf schema definition and the generated encoding logic could cause:

• Serialization/deserialization errors
• Network protocol incompatibility
• Transaction broadcast failures when using MsgCall with arguments

Changes

• Updated MsgCall.encode() method to use correct tag number 50 for the args field
• This ensures proper serialization compatibility with the protobuf schema

[zivkovicmilos]

Good catch.

I'm sure this is leftover from the manual changes we are propagating out after #46.

#187 will fix these issues, hopefully