[UNIT]test: add unit test cases for interpreter to improve coverage

[kylo5aby]

Summary

To quickly improve WAMR's software quality, this PR uses LLM to generate unit test cases for the interpreter module.

Changes

• Add 15 new unit test cases for iwasm/interpreter module
• Improve iwasm/interpreter coverage:
  • Lines coverage: 33.7% → 35.0% (+1.3%)
  • Functions coverage: 55.4% → 56.2% (+0.8%)

Testing

All new test cases pass successfully.

Welcome any feedback or suggestions on these AI-generated test cases. Please let me know if you have ideas for improvement.

[lum1n0us]

Preferably store all those test cases in a separate directory, such as smart-tests or digit-suite.

please co-sign with ai-assistant in the git comment. https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors#creating-co-authored-commits-on-the-command-line

[lum1n0us]

Invalid assertion.

[yamt]

i'd suggest that anyone who wants to submit an AI-generated thing should review it by himself extensively before making it be publicly reviewed.
reviewing AI-generated logic is tiresome.

[lum1n0us]

The file and directory structure should be organized as follows:

unit
├── CMakeLists.txt              -> add_subdirectory(smart-cases)
└── smart-cases
    ├── CMakeLists.txt          -> add_subdirectory(interpreter)
    └── interpreter
        ├── CMakeLists.txt
        └── wasm-apps

[lum1n0us]

IMO, ideally, for a function, there should be one positive case, one negative case, and one corner case for testing.