fix!: dirty hack to signing successfully the first data commitment range

[rach-id]

Overview

This is because we included the latest core release in the app v0.13.2 without including the corresponding change in the state machine.

For BSR, this case will never be hit since we will stop at the last unbonding height. But, I think it's better if we have the E2E passing to be more sure this is working.

Checklist

• New and updated code has appropriate documentation
• New and updated code has new and/or updated testing
• Required CI checks are passing
• Visual proof for any user facing features like CLI or documentation updates
• Linked issues closed with keywords

[evan-forbes]

cool, can we have an issue to revert this eventually too? thanks!

[rach-id]

This will be only for this release... won't be merged to main. So I guess no need for an issue. What do you think? @evan-forbes

[codecov-commenter]

Codecov Report

❗ No coverage uploaded for pull request base (v0.2.0-app-v0.13.2-beta@765ef7d). Click here to learn what that means.
The diff coverage is n/a.

@@                    Coverage Diff                     @@
##             v0.2.0-app-v0.13.2-beta     #340   +/-   ##
==========================================================
  Coverage                           ?   43.57%           
==========================================================
  Files                              ?       26           
  Lines                              ?     1999           
  Branches                           ?        0           
==========================================================
  Hits                               ?      871           
  Misses                             ?     1005           
  Partials                           ?      123