Allow to call init and debug inner field in a test module

[yanganto]

Steps to Reproduce Issue

The following repo shows the restrictions about the testcase in a different file.
https://github.com/yanganto/SuiMoveTestIssue

The demo1 and demo2 are the same, and the testcases are the same, the only different is one is in the module and the other is in the test module.

1. Call sui move test under /demo1
2. Call sui move test under /demo2

Expected Result

Expected the demo2 should pass.
Specify what outcome you expected should have resulted, but didn't.

Actual Result

The test of demo2 fails, due to the visibility issue.

System Information

• OS: NixOS
• Compiler: Rust 1.81

[yanganto]

Hi, I update the readme of the repo, and also propose a solution for this.
https://github.com/yanganto/SuiMoveTestIssue/pull/3/files

If this proposal looks good, and the issue is a not urgent one, I will happy to work on this and make a PR here.

[yanganto]

After a deep look at this issue. The previous proposal is not a good one and the SuiInit is good.

Can we let this go first with debug_assertions? Because we can easily have a special debug build of sui-move without bytecode verifier support at this moment, it will solve the current use case and also the test coverage in quick without any burden on product level, and it will really kind for a contract developer and help us build the ecosystem and community. I am also happy to address this issue.

#20482 is for this idea, and it works shown in CI of yanganto/SuiMoveTestIssue#4