feat(cli.rs): allow passing arguments to the build runner, closes #3398

[lucasfernog]

What kind of change does this PR introduce?

• Bugfix
• Feature
• Docs
• New Binding issue #___
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change?

• Yes, and the changes were approved in issue #___
• No

Checklist

• When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
• A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
• I have added a convincing reason for adding this feature, if necessary

Other information

[amrbashir]

What about tauri dev? I think the author of the issue wanted that.

[lucasfernog]

What about tauri dev? I think the author of the issue wanted that.

Tauri dev is tricky because we're already using the -- <ARGS> approach to pass commands to the binary. So maybe we change dev to work the same way as build, which already comes with support to passing args to the binary (tauri dev -- --frozen -- --arg-to-binary. Ugly but it works.

[amrbashir]

yeah, I hardly think anyone uses it but so we don't introduce any breaking change we could do something like this
tauri build/dev --cargo-args="-vvv -Z unstable-options"

the name could be better

[amrbashir]

So maybe we change dev to work the same way as build, which already comes with support to passing args to the binary (tauri dev -- --frozen -- --arg-to-binary. Ugly but it works.

or that

[lucasfernog]

I went with a small breaking change, now is the time anyway. Keeping the syntax the same is more important IMO.