fix: unable to connect ledger nano S on Ubuntu

[jaeseung-bae]

Description

closes: #1039

• The latest version for github.com/cosmos/ledger-cosmos-go is v0.13.0. The latest version breaks some interfaces so I bump up with v0.12.2(the second latest one) which is enough to fix the issue.

Motivation and context

• "failed to retrieve device: ledger nano S: no ledger connected" on ubuntu 20.04, 22.04 #1039

How has this been tested?

• I tested with a nano S plus ledger on both Ubuntu 20.04 and Mac

Screenshots (if appropriate):

Checklist:

• I followed the contributing guidelines and code of conduct.
• I have added a relevant changelog to CHANGELOG.md
• I have added tests to cover my changes.
• I have updated the documentation accordingly.
• I have updated API documentation client/docs/swagger-ui/swagger.yaml

[zemyblue]

I think this PR is duplicated with #1027 .
The #1027 PR bumps up ledger-cosmos-go to v0.13.0

What shall we do in order to use ledger-cosmos-go v0.13.0?

[jaeseung-bae]

I think this PR is duplicated with #1027 . The #1027 PR bumps up ledger-cosmos-go to v0.13.0

What shall we do in order to use ledger-cosmos-go v0.13.0?

From v0.13.0, interface SECP256K1's SignSECP256K1 function has changed.
v0.13.0 introduces feat!: Add SIGN_MODE_TEXTUAL
In order to use v0.13.0, some of code that use SignSECP256K1() must be changed for compile.

SECP256K1 interface {
		SignSECP256K1([]uint32, []byte) ([]byte, error) // v0.12.2
		SignSECP256K1([]uint32, []byte, byte) ([]byte, error) // v0.13.0
}

[jaeseung-bae]

@zemyblue, Do you think It is better to change the code to adapt v0.13.0 from PR #1027.

[zemyblue]

@zemyblue, Do you think It is better to change the code to adapt v0.13.0 from PR #1027.

Yes, but I think we cannot use v0.13.0 in this case.
I want to know why v0.13.0 can't.