refactor: add named interface for type alias

[mmsqe]

to avoid cannot handle non-empty unnamed interfaces error when mockgen -package mock -destination store/mock/cosmos_cosmos_db_DB.go github.com/cosmos/cosmos-db DB

Summary by CodeRabbit

• Refactor
  • Updated internal interface naming for improved clarity while maintaining compatibility with existing type names. No changes to functionality or behavior.

[coderabbitai]

Walkthrough

The changes rename the Batch and Iterator interfaces in types.go to BatchI and IteratorI, respectively. Type aliases are then introduced so that Batch becomes an alias for BatchI and Iterator becomes an alias for IteratorI. The method signatures and interface contracts remain unchanged; only the primary type names are updated, with the original names preserved as aliases for compatibility.

Changes

File(s)	Change Summary
types.go	Renamed Batch interface to BatchI and Iterator to IteratorI; added type aliases for both

Possibly related issues

• [Bug]: cannot handle non-empty unnamed interfaces in mockgen cosmos-sdk#24464: Addresses interface renaming and type aliasing, matching the changes in this PR.

Possibly related PRs

• chore: make a type alias in DB interface #114: Also modifies Batch and Iterator interface declarations and introduces type aliases, directly related to this PR.

Suggested reviewers

• tac0turtle

Poem

In the meadow of code, I hop with glee,
Renaming interfaces as neat as can be.
BatchI and IteratorI now lead the way,
While old names as aliases happily stay.
A gentle refactor, not a bug in sight—
This rabbit’s work is tidy and light!
🐇✨

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dfd3925 and 8603d28.

📒 Files selected for processing (1)

• types.go (4 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• types.go

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[aljo242]

@mmsqe lint failing

[mmsqe]

@mmsqe lint failing

Seems fail before, not related to this change. I open a separate #128 to make lint ci green.