refactor: remove bytes/HexBytes

[chixiaowen]

Description

Closes: #15049

this pr has removed bytes/HexBytes in cosmos-sdk

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[chixiaowen]

I can not remove only one place，follow :
path: testutil/cli/cmt_mocks.go
func: func (m MockCometRPC) ABCIQueryWithOptions

because I need to modify package of cometbft

[tac0turtle]

super nice docs, it looks good to me. It doesnt seem like we use the json encoding anywhere i can see.

[chixiaowen]

super nice docs, it looks good to me. It doesnt seem like we use the json encoding anywhere i can see.

It seems that cmtbytes does not use func of MarshalJSON() nor UnmarshalJSON(), only use of the func String(), so that I do not use json encoding.

[facundomedica]

fmt.Sprintf("%X", e.Hash()) seems to be faster than strings.ToUpper(hex.EncodeToString(e.Hash())). Any objections to using fmt?

Note: hex.EncodeToString by itself is faster but because we do strings.ToUpper it's the other way around.

[chixiaowen]

strings.ToUpper(hex.EncodeToString(e.Hash()))

@facundomedica I have made a bench test,
`func Benchmark_Fmt(b *testing.B) {
e := []byte("hello")
for i := 0; i < b.N; i++ {
fmt.Sprintf("%X", e)
}
}

func Benchmark_Hex(b *testing.B) {
e := []byte("hello")
for i := 0; i < b.N; i++ {
hex.EncodeToString(e)
}
}

func Benchmark_Shex(b *testing.B) {
e := []byte("hello")
for i := 0; i < b.N; i++ {
strings.ToUpper(hex.EncodeToString(e))
}
}`
and the result as follow:

goos: darwin
goarch: amd64
pkg: mytest/struct_01
cpu: Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
Benchmark_Fmt
Benchmark_Fmt-16 9034696 125.7 ns/op
Benchmark_Hex
Benchmark_Hex-16 49447454 23.87 ns/op
Benchmark_Shex
Benchmark_Shex-16 18752376 64.16 ns/op
PASS

It seems that strings.ToUpper(hex.EncodeToString(e.Hash())) is faster than fmt.Sprintf("%X", e.Hash())`

[julienrbrt]

lgtm! We can fix the proto lint and some other things in a follow-up.
Thank you!

[atheeshp]

Suggested change

	There is something changed.Due to the import changes, this is a breaking change. Chains need to remove **entirely** their imports in their codebase, from direct and indirects imports.
	There is something changed. Due to the import changes, this is a breaking change. Chains need to remove **entirely** their imports in their codebase, from direct and indirects imports.

[julienrbrt]

I am going to merge this now (we can improve in a follow-up).
Thank you, @chixiaowen, for your contribution!