chore: update codeowners for third party team

[hedi-edelbloute]

✅ Checklist

• npx changeset was attached. => not applicable
• Covered by automatic tests. => not applicable
• Impact of the changes:
  • codeowners

📝 Description

Update to match the new setup with third-party-leads team, replaces current setup where coin-integration leads are in each partner team

❓ Context

• JIRA or GitHub link:
• ADR link (if any):

---

🧐 Checklist for the PR Reviewers

• The code aligns with the requirements described in the linked JIRA or GitHub issue.
• The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
• There are no undocumented trade-offs, technical debt, or maintainability issues.
• The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
• Any new dependencies have been justified and documented.
• Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

[github-actions]

Web Tools Build Status

Build	Status	Deployment
Web Tools Build	⏭️ Skipped	—
Native Storybook Build	⏭️ Skipped	—
React Storybook Build	⏭️ Skipped	—

[Copilot]

Pull request overview

Updates repository ownership rules to reflect the new ledger-third-party-leads team setup for partner-related coin modules, ensuring the new team is included as a reviewer/owner for relevant directories.

Changes:

• Add @ledgerhq/ledger-third-party-leads as an additional CODEOWNER for selected libs/coin-modules/* partner/shared coin directories.
• Keep existing ownership by @ledgerhq/blockchain-support and the partner teams, while extending ownership to the new leads team.