test: add native wrap and install e2e workflows

[JerrettDavis]

Summary

• add a cross-platform wrap native e2e workflow that runs the existing prepare-only bridge tests on linux, macos, and windows
• add a cross-platform install native e2e workflow that runs safe install CLI smoke tests on real runners
• reuse the shared native e2e setup action so these workflows stay aligned with the init-native pattern

Testing

• ..uv-venv\Scripts\python.exe -m pytest tests/test_cli/test_wrap_bridge.py tests/test_cli/test_install_cli.py tests/test_install/test_paths.py -q
• act workflow_dispatch -W .github/workflows/wrap-native-e2e.yml -n
• act workflow_dispatch -W .github/workflows/install-native-e2e.yml -n

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[chopratejas]

Hi @JerrettDavis - can you resolve the conflicts here?
Thanks

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
32448684	Triggered	JSON Web Token	993d37c	crates/headroom-core/benches/auth_mode.rs	View secret
32448685	Triggered	Bearer Token	993d37c	crates/headroom-core/benches/auth_mode.rs	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[github-actions]

This pull request has had no recent activity and is being marked stale. Please rebase, resolve conflicts, or comment if it is still actively being worked.

[JerrettDavis]

@copilot resolve the merge conflicts in this pull request