feat(gnovm): add gno fuzz for gno test

[rlaau]

Title: Add Fuzzing Support for cmd with Enhanced Options

Description:
This PR introduces a fuzzing mechanism to the cmd following Go's fuzzing approach. The new functionality includes the following features and usage:

Usage:

1. Command: cmd supports a fuzzing mechanism similar to Go's built-in fuzzing framework.
2. FuzzXXX Function:
   • The FuzzXXX function should follow the standard signature where f.Fuzz accepts a function with the format:

     f.Fuzz(func(t *testing.T, orig ...interface{}) {})

Example Code:

func FuzzMock(f *testing.F) {
    f.Add("apple hello", int(400002131323))
    f.Add("rainy day", int(98401132231331))
    f.Add("winter comes", int(12349123123))
    f.Fuzz(func(t *testing.T, orig ...interface{}) {
        v, ok := orig[0].(string)
        if !ok {
            panic("type mismatch")
        }
        i, ok2 := orig[1].(int)
        if !ok2 {
            panic("type mismatch")
        }
        rev := testing.Reverse1(v)
        doubleRev := testing.Reverse1(rev)
        if v != doubleRev && i > 300 && i < 500 {
            t.Errorf("Before: %q, after: %q", orig, doubleRev)
        }
        if utf8.ValidString(v) && !utf8.ValidString(rev) && i > 300 && i < 1000 {
            t.Errorf("Reverse produced invalid UTF-8 string %q", rev)
        }
    })
}

### Example Command:
```bash
gno test mock_test.gno -fuzz=Fuzz -v

Input: ["\xce", 318]
Panic/Error: Error 
ErrorMessage: "Before: ["\xce" 'ľ'], after: "�""

Changes Introduced:
Added -fuzz flag for fuzz testing in the cmd.
Enhanced support for verbose output (-v) and iteration specification (-i).

[Gno2D2]

🛠 PR Checks Summary

All Automated Checks passed. ✅

Manual Checks (for Reviewers):

• IGNORE the bot requirements for this PR (force green CI check)
• The pull request description provides enough details

Read More

🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers.

✅ Automated Checks (for Contributors):

🟢 Maintainers must be able to edit this pull request (more info)

☑️ Contributor Actions:

1. Fix any issues flagged by automated checks.
2. Follow the Contributor Checklist to ensure your PR is ready for review.
   • Add new tests, or document why they are unnecessary.
   • Provide clear examples/screenshots, if necessary.
   • Update documentation, if required.
   • Ensure no breaking changes, or include BREAKING CHANGE notes.
   • Link related issues/PRs, where applicable.

☑️ Reviewer Actions:

1. Complete manual checks for the PR, including the guidelines and additional checks if applicable.

📚 Resources:

• Report a bug with the bot.
• View the bot’s configuration file.

Debug

Automated Checks

Maintainers must be able to edit this pull request (more info)

If

🟢 Condition met
└── 🟢 The pull request was created from a fork (head branch repo: rlaau/gno)

Then

🟢 Requirement satisfied
└── 🟢 Maintainer can modify this pull request

Manual Checks

**IGNORE** the bot requirements for this PR (force green CI check)

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

• Any user with comment edit permission

The pull request description provides enough details

If

🟢 Condition met
└── 🟢 Not (🔴 Pull request author is a member of the team: core-contributors)

Can be checked by

• team core-contributors