docs: remove misnamed duplicate contribution guide

[xiakong130]

What changed

Removed CONTRIUBUTION.md — a misnamed duplicate of the contribution guide.

Why

• The filename has a typo: CONTRIUBUTION instead of CONTRIBUTION
• The file content is a generic template with placeholder URLs (your-username/project-name), not specific to Reframe
• The authoritative contribution guide already exists as CONTRIBUTING.md, which is complete and project-specific
• Two contribution guide files with different names causes confusion

How I checked

• Confirmed CONTRIBUTING.md (the authoritative guide) still exists and is untouched
• Searched the entire repo for references to CONTRIUBUTION.md — none found, so no broken links are introduced
• The deleted file's content is fully superseded by CONTRIBUTING.md

[vercel]

@xiakong130 is attempting to deploy a commit to the magic-peach1's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

👋 Thanks for your PR, @xiakong130!

Welcome to Reframe — a browser-based video editor built for everyone 🎬

What happens next

1. 🤖 Automated checks — build & TypeScript typecheck will run automatically
2. ✅ Vercel preview — a preview deployment will be created (requires maintainer authorization for fork PRs)
3. 👀 Code review — a maintainer will review your changes
4. 🚀 Merge — once approved, your PR will be merged!

Quick checklist

• PR title follows Conventional Commits (e.g. feat: add dark mode)
• Linked the issue this PR closes (e.g. Closes #123)
• Tested the changes locally (bun run dev)
• Build passes (bun run build)

Useful links

• 📖 CONTRIBUTING.md
• 🐛 Open Issues
• ⭐ Star the repo to support the project!

Happy coding! 🎉

[github-actions]

⚠️ PR Format Issues — @xiakong130

Please fix the following before your PR can be reviewed:

• ⚠️ No linked issue found. Add Closes #<issue-number> to your PR description.

Push new commits after fixing — this comment will update automatically.

📖 CONTRIBUTING.md

[github-actions]

👋 This PR has been inactive for 21 days. It will be automatically closed in 14 days if there's no further activity.

If you need help with this PR, please comment or ping a maintainer.
Make sure your branch is rebased onto main and all CI checks pass.