fix(dojo-lang): add all crates to test database for Cairo test runner

[glihm]

Ensure all the crates are added to the database built for the cairo lang test runner. This ensures all the types defined in a dependency are actually found.

Summary by CodeRabbit

• New Features

  • Enhanced the spawn_test_world function to support multiple namespaces, improving functionality and flexibility in model handling.
  • Added new support for the flatbow model in test scenarios, expanding the test coverage.

• Bug Fixes

  • Improved robustness of the testing framework by refining how input types are handled in function calls.

• Chores

  • Updated configuration files to include new contract components and mappings for improved organization and access.

[coderabbitai]

Walkthrough

Ohayo, sensei! The recent changes enhance the testing framework by improving how crate IDs and namespaces are collected and utilized. Key modifications include transitioning to the use of spans for arrays and strings, which boosts type safety and performance. The updates also introduce new models into test scenarios, creating a more robust and flexible testing environment. Overall, these enhancements aim to improve the clarity, maintainability, and functionality of the codebase.

Changes

Files	Change Summary
bin/sozo/src/commands/test.rs	Replaced collect_main_crate_ids with collect_all_crate_ids for broader crate ID collection. Refactored CompiledTestRunner instantiation for improved readability.
crates/dojo-core/src/tests/base.cairo, crates/dojo-core/src/tests/helpers.cairo, crates/dojo-core/src/tests/world/resources.cairo, crates/dojo-core/src/tests/world/world.cairo	Updated deploy_world and other functions to use span() instead of arrays, enhancing type safety and performance while keeping functional behavior intact.
crates/dojo-core/src/utils/test.cairo	Changed spawn_test_world to accept a Span<ByteArray> for multiple namespaces instead of a single ByteArray. Updated internal logic to register multiple namespaces dynamically.
examples/spawn-and-move/Scarb.toml	Added a new external contract "origami_token::components::introspection::src5::SRC5Model" to build-external-contracts, enhancing functionality.
examples/spawn-and-move/dojo_dev.toml	Added mapping for "origami_token" to dojo_examples_origami, improving organization and access to models.
examples/spawn-and-move/src/actions.cairo	Introduced flatbow model into tests, updated model hashes in the testing setup, and modified spawn_test_world invocation to include spans for world names, enhancing flexibility and specificity of test scenarios.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant TestFramework
    participant CrateCollector
    participant WorldManager

    User->>TestFramework: Initiate Test
    TestFramework->>CrateCollector: Collect All Crate IDs
    CrateCollector-->>TestFramework: Return Crate IDs
    TestFramework->>WorldManager: Spawn Test World
    WorldManager-->>TestFramework: Return World Object
    TestFramework-->>User: Complete Test Execution

Loading

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.60%. Comparing base (ebed9bd) to head (a936268).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2296   +/-   ##
=======================================
  Coverage   69.59%   69.60%           
=======================================
  Files         352      352           
  Lines       46036    46037    +1     
=======================================
+ Hits        32040    32042    +2     
+ Misses      13996    13995    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.