fix: BondedTokens exceeds int64 range

[huichiaotsou]

Description

Closes: #XXXX

fix bonded tokens / unbonded tokens exceeding range with int64.
Store the value as string instead.

---

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
• provided a link to the relevant issue or specification
• 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 API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[codecov-commenter]

Codecov Report

❗ No coverage uploaded for pull request base (v2/cosmos/stargate@1bdca6c). Click here to learn what that means.
The diff coverage is n/a.

@@                  Coverage Diff                  @@
##             v2/cosmos/stargate     #300   +/-   ##
=====================================================
  Coverage                      ?   50.58%           
=====================================================
  Files                         ?       19           
  Lines                         ?     1870           
  Branches                      ?        0           
=====================================================
  Hits                          ?      946           
  Misses                        ?      796           
  Partials                      ?      128           

[MonikaCat]

@huichiaotsou Can you also update the schema for proposal_staking_pool_snapshot table ?

[huichiaotsou]

@huichiaotsou Can you also update the schema for proposal_staking_pool_snapshot table ?

Hi hi @MonikaCat I found out that the type we use in staking_pool table is also BIGINT, should I update both or we can keep BIGINT for both tables?

[MonikaCat]

@huichiaotsou Yes let's update the staking_pool table to TEXT type as well, coz on some chains this value might also be too large to store as a BIGINT

[MonikaCat]

LGTM

[RiccardoM]

utACK