feat(cmd): gno mod module name validations

[notJoon]

Description

Added module path validation to prevent invalid characters from being written to gno mod initialization.

The validation:

1. Checks for non-ASCII characters
2. Validates against specific invalid characters (``, ", , ?, *, :, <, >, |, [, ]`)
3. Prevents spaces and control characters
4. Ensures the module path is not empty

Implementation Details

1. Added validateModulePath function with comprehensive validation rules
2. Integrated validation into execModInit

Added Tests

• TestValidateModulePath: Tests various validation scenarios including

  • Valid module paths (including gno.land paths)
  • Invalid UTF-8 characters
  • Spaces in paths
  • Special characters
  • Empty paths
  • Various invalid characters

• TestExecModInit: Integration tests covering

  • Successful module initialization
  • Various invalid path scenarios
  • Error cases (existing gno.mod, too many arguments)

Relative Issue

closes #3493

[Gno2D2]

🛠 PR Checks Summary

All Automated Checks passed. ✅

Manual Checks (for Reviewers):

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

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)
🟢 Pending initial approval by a review team member (and label matches review triage state)

☑️ 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: notJoon/gno-core)

Then

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

Pending initial approval by a review team member (and label matches review triage state)

If

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

Then

🟢 Requirement satisfied
└── 🟢 If
    ├── 🟢 Condition
    │   └── 🟢 Or
    │       ├── 🟢 At least 1 user(s) of the organization approved the pull request
    │       └── 🔴 This pull request is a draft
    └── 🟢 Then
        └── 🟢 Not (🔴 This label is applied to pull request: review/triage-pending)

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

[jefft0]

@notJoon , can you resolve the CI check for "gno.land / Run gno.land suite / Go Test" ?

[notJoon]

@jefft0 Thanks for notifying me. Now all issues have been resolved except for the review-triage stage.

[jefft0]

This PR appears to correctly address and resolve issue #3493 . A test is included. All CI checks pass (except "Merge Requirements" which will be resolved later).

[jefft0]

Removed the review/triage-pending label. Ready to be reviewed by core devs, possibly including @kristovatlas who created issue #3493 which this PR resolves.