ci: update sonar project key

[NelsonBN]

Checklist before requesting a review

• I have performed a self-review of my code.
• Implemented tests for new features.
• I tested the features already implemented.
• Added usage examples in the readme.

[Copilot]

Copilot review overview

🟢 Approval recommended

The corrected key is consistently documented and correctly passed to the Sonar scanner.

Review effort: Balanced
Findings: None

What changed in this PR

Updates the CI workflow to target the repository’s correct SonarCloud project.

Changes:

• Aligns the SonarCloud project key with the README badge configuration.

File	Description
.github/​workflows/​sonarcloud-and-mutations.yml	Updates the SonarCloud project identifier.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[github-actions]

🚀 Stryker report generated 🚀

To more details: https://dashboard.stryker-mutator.io/reports/github.com/TechNobre/PowerUtils.Geolocation/improve-sonarcloud-374

[github-actions]

Package	Line Rate	Branch Rate	Complexity	Health
PowerUtils.Geolocation	100%	99%	131	✔
Summary	100% (181 / 181)	99% (69 / 70)	131	✔

[github-actions]

Test Summary

    5 files      5 suites   1s ⏱️
  252 tests   252 ✅ 0 💤 0 ❌
1 260 runs  1 260 ✅ 0 💤 0 ❌

Results for commit ede7edc.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud