build: update golang version to 1.20

[0Tech]

Description

closes: #1024

Motivation and context

How has this been tested?

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

[codecov]

Codecov Report

Merging #1043 (64d6b8a) into main (73cf295) will increase coverage by 0.01%.
The diff coverage is 70.27%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1043      +/-   ##
==========================================
+ Coverage   62.01%   62.02%   +0.01%     
==========================================
  Files         656      656              
  Lines       78937    78937              
==========================================
+ Hits        48950    48961      +11     
+ Misses      27298    27287      -11     
  Partials     2689     2689              

Impacted Files	Coverage Δ
crypto/keyring/keyring.go	58.07% <0.00%> (ø)
x/foundation/client/testutil/tx.go	100.00% <ø> (ø)
x/foundation/codec.go	100.00% <ø> (ø)
x/foundation/keeper/internal/keys.go	98.11% <ø> (ø)
x/foundation/keeper/internal/msg_server.go	87.20% <ø> (ø)
x/foundation/msgs.go	67.80% <ø> (ø)
x/foundation/foundation.go	84.30% <9.09%> (ø)
x/foundation/keeper/internal/migrations.go	50.00% <33.33%> (ø)
x/auth/keeper/grpc_query.go	57.14% <62.50%> (ø)
x/auth/keeper/keeper.go	74.78% <86.66%> (ø)
... and 4 more

... and 2 files with indirect coverage changes

[0Tech]

I MUST revert the replace on ostracon.

[0Tech]

Or, we should merge #1025 into main and deal with the differences between 1.19 and 1.20.

What do you think @zemyblue ?

[zemyblue]

Or, we should merge #1025 into main and deal with the differences between 1.19 and 1.20.

What do you think @zemyblue ?

No I think it's not a good idea.