Add Copilot support and fix Windows startup

[timeshift92]

Add explicit GitHub Copilot integration for both repository-local and global setup, wire the Copilot hook asset to
tk hook copilot, document the new workflow, and add focused tests for the new assets and CLI parsing.

Also fix the Windows startup stack overflow by reserving a larger main-thread stack at link time so
tk.exe --version, --help, and Copilot hook entry points start reliably on Windows.

Summary

Test plan

• cargo fmt --all && cargo clippy --all-targets && cargo test
• Manual testing: rtk <command> output inspected

Important: All PRs must target the develop branch (not master).
See CONTRIBUTING.md for details.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Ахмедов Нурбек Медетбаевич seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[pszymkowiak]

[w] wshm · Automated triage by AI

📊 Automated PR Analysis

✨ Type	feature
🟡 Risk	medium

Summary

Adds explicit GitHub Copilot integration with both global and repository-local setup modes, updates the hook command from 'rtk hook' to 'rtk hook copilot', and fixes a Windows startup stack overflow by reserving an 8 MiB main-thread stack at link time in build.rs.

Review Checklist

• Tests present
• Breaking change
• Docs updated

---

Analyzed automatically by wshm · This is an automated analysis, not a human review.

[pszymkowiak]

Thanks @timeshift92 for the effort!

Copilot support is already shipped — we merged Copilot integration (hooks, awareness docs, rtk init --agent copilot) in v0.31.0. Closing this PR as the main feature already exists.

However, the Windows stack fix in build.rs is valuable. We've opened a dedicated issue for it (#849) — if you'd like to submit a small PR with just that change targeting develop, we'd be happy to merge it.

Thanks for contributing!

[hemantkamalakarhaltian]

+1

[timeshift92]

#865