Build and execute any filesystem path

[intelliot]

High Level Overview of Change

Enable the craft build command to build and execute WASM modules from any filesystem path, not just the current directory or predefined project locations.

Fix #199

Context of Change

Previously, it was difficult to work with WASM projects located elsewhere on the filesystem.

The fix modifies the build command to accept and properly handle absolute and relative filesystem paths, allowing developers to build WASM modules from any location. This provides greater flexibility in project organization and development workflows.

Type of Change

• New feature (non-breaking change which adds functionality)
• Tests (You added tests for code that already exists, or your new feature included in this PR)

Release Note

The craft build command now supports building WASM modules from any filesystem path. Users can specify absolute or relative paths to build projects.

[Copilot]

Pull Request Overview

This PR enables the craft build command to build and execute WASM modules from any filesystem path, addressing issue #199. It adds flexibility for developers to work with WASM projects located anywhere on the filesystem.

• Adds --path option to craft build command for specifying arbitrary project directories
• Introduces new craft execute command for running pre-built WASM files
• Updates WASM host simulator to accept explicit WASM file paths via --wasm flag

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
craft/src/main.rs	Adds --path flag to build command and new execute subcommand with CLI argument parsing
craft/src/utils/mod.rs	Improves project name detection by reading from Cargo.toml instead of relying on directory name
craft/src/commands/mod.rs	Implements execute_wasm function for running pre-built WASM files
craft/src/commands/test.rs	Updates test runner to handle both directory and WASM file paths
wasm-host-simulator/src/main.rs	Adds --wasm argument for direct WASM file execution

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Pull Request Overview

Copilot reviewed 6 out of 7 changed files in this pull request and generated 2 comments.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[intelliot]

(only rebased on main)

[sappenin]

@intelliot Can you give some examples of how this new feature is supposed to work. I'm not able to see this in action in the CLI prompts.

[intelliot]

craft build --path /external/path
craft execute --wasm /path/to/file.wasm

To execute with the wasm_host_simulator, it currently still requires test data fixtures, but that's a separate problem

[intelliot]

External projects (not using craft workspace) need the https://github.com/ripple/craft/blob/main/rust-toolchain.toml file in order to use wasm32v1-none

[sappenin]

This PR is no longer in-scope. Please see https://github.com/ripple/xrpl-wasm-std for now and feel free to re-open a PR like this one in that project, if appropriate (we may revisit a CLI in the future, but for now are continuing work on the XRPL WASM standard library in that project).