Add Leverage To the Protocol (backport #3079)

[mergify]

Changelist

[Describe or list the changes made in this PR]

Test Plan

[Describe how this PR was tested (if applicable)]

Author/Reviewer Checklist

• If this PR has changes that result in a different app state given the same prior state and transaction list, manually add the state-breaking label.
• If the PR has breaking postgres changes to the indexer add the indexer-postgres-breaking label.
• If this PR isn't state-breaking but has changes that modify behavior in PrepareProposal or ProcessProposal, manually add the label proposal-breaking.
• If this PR is one of many that implement a specific feature, manually label them all feature:[feature-name].
• If you wish to for mergify-bot to automatically create a PR to backport your change to a release branch, manually add the label backport/[branch-name].
• Manually add any of the following labels: refactor, chore, bug.

Summary by CodeRabbit

• New Features

  • Per-subaccount leverage management: submit UpdateLeverage transactions (CLI tx command, Msg RPC) and fetch leverage via new Leverage query (gRPC/LCD/CLI).

• Rate Limiting

  • Configurable per‑N‑block leverage‑update limits added to genesis/config and validated; enforced during CheckTx with a dedicated leverage rate limiter.

• Tests

  • E2E and rate‑limit tests added to validate leverage flows and enforcement.

---

This is an automatic backport of pull request #3079 done by [Mergify](https://mergify.com).

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}