chore: move fuzz testing under tests

[aljo242]

• move the fuzz folder into tests
• delete dead script and patch file

Summary by CodeRabbit

• Tests

  • Removed obsolete internal tests to streamline our quality assurance process.

• Chores

  • Cleaned up legacy automation scripts for fuzz testing to enhance overall maintainability.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes remove two key components from the codebase. The first deletion is from the address testing file, which contained a suite of tests for Bech32 address encoding functions including normal and error-case scenarios. The second deletion removes the fuzz testing build script that automated environment setup, dependency configuration, and compilation processes for Cosmos SDK fuzz tests.

Changes

File(s)	Change Summary
types/address_test.go	Removed the address test suite including functions TestAddressTestSuite, TestBech32ifyAddressBytes, and TestMustBech32ifyAddressBytes.
fuzz/oss-fuzz-build.sh	Deleted the shell script that automated the setup, organization, and compilation of fuzz tests for the Cosmos SDK.

---

📜 Recent review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 738f288 and a0d1e65.

📒 Files selected for processing (2)

• fuzz/fuzz.patch (0 hunks)
• fuzz/oss-fuzz-build.sh (0 hunks)

💤 Files with no reviewable changes (2)

• fuzz/oss-fuzz-build.sh
• fuzz/fuzz.patch

⏰ Context from checks skipped due to timeout of 90000ms (14)

• GitHub Check: tests (03)
• GitHub Check: tests (02)
• GitHub Check: tests (01)
• GitHub Check: tests (00)
• GitHub Check: test-simapp-v2
• GitHub Check: test-system-v2
• GitHub Check: test-sim-nondeterminism
• GitHub Check: test-integration
• GitHub Check: build (arm64)
• GitHub Check: build (amd64)
• GitHub Check: Analyze
• GitHub Check: dependency-review
• GitHub Check: golangci-lint
• GitHub Check: Summary

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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. (Beta)
• @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.

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.

[julienrbrt]

ACK, but a go mod tidy is needed.