feat(bundler): check target arch at runtime, closes #2286

[lucasfernog]

What kind of change does this PR introduce? (check at least one)

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

Does this PR introduce a breaking change? (check one)

• Yes. Issue #___
• No

The PR fulfills these requirements:

• When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
• A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

[lucasfernog]

I don't have a macOS M1 to test this but it should fix #2286.

[chrisspiegl]

I am wondering if this is already in the public release.
I am using @tauri-apps/cli@1.0.0-beta.10 and it's still behaving as before.
But I also can't seem to test since the current stuff on github is not release to npm at all and I have not yet found a way to get the repository installed via git links in my package.json.

[FabianLars]

@chrisspiegl It should be yes, make sure it actually resolves to beta.10 in your lock file.
For testing the unreleased stuff see my answer to your comment in #2510.

via git links in my package.json

As mentioned in the other issue that wouldn't help you anyway