Disable lsm unbond

[joe-bowman]

Remove LSM unbonding given it's unreliability, and always use native unbonding.

[codecov]

Codecov Report

Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (ff3146a) 61.78% compared to head (0cff9cc) 61.44%.
Report is 5 commits behind head on main.

❗ Current head 0cff9cc differs from pull request most recent head 28eedd0. Consider uploading reports for the commit 28eedd0 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #997      +/-   ##
==========================================
- Coverage   61.78%   61.44%   -0.35%     
==========================================
  Files         172      172              
  Lines       14134    14118      -16     
==========================================
- Hits         8733     8675      -58     
- Misses       4651     4697      +46     
+ Partials      750      746       -4     

Flag	Coverage Δ
unittests	61.44% <0.00%> (-0.35%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
x/interchainstaking/keeper/msg_server.go	84.61% <0.00%> (-0.37%)	⬇️

... and 3 files with indirect coverage changes

[faddat]

Do you think this should result in any upstream fixes?

[faddat]

Great catch we love to live reliable

[joe-bowman]

Do you think this should result in any upstream fixes?

No, just LSM unbonding is a much more complex math problem, as the user receives bonded tokens back, and you need to compromise somewhere between what is best for the protocol, and what is best for the user (not receiving buckets of dust). It requires a little more finesse.

[faddat]

finesse