chore(testing): Switch coverage reporting from Codecov to SonarCloud

[hckhanh]

Replace Codecov integrations with SonarCloud for coverage reporting and static code analysis. Add sonar-project.properties to configure SonarCloud reporting paths. Update GitHub Actions workflow to execute SonarCloud scans, removing Codecov steps.

Summary by Sourcery

Replace Codecov with SonarCloud for coverage reporting and static code analysis, updating GitHub Actions workflow and configuration files accordingly.

CI:

• Switch from Codecov to SonarCloud for coverage reporting and static code analysis in GitHub Actions workflow.

Documentation:

• Remove Codecov badge from README.md.

Chores:

• Add sonar-project.properties file to configure SonarCloud reporting paths.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR transitions the project's code coverage and analysis tooling from Codecov to SonarCloud. The implementation involves removing Codecov-related GitHub Actions steps, configuring SonarCloud properties, and adjusting the test reporting formats to match SonarCloud's requirements. The changes also include adding ESLint JSON reporting to integrate with SonarCloud's static analysis capabilities.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Replace Codecov with SonarCloud in GitHub Actions workflow	Remove Codecov coverage upload action Remove Codecov test results upload action Add SonarCloud scan action Add ESLint execution step	.github/workflows/tests.yml
Update test configuration for SonarCloud compatibility	Change coverage reporter from 'clover' to 'lcovonly' Simplify CI reporters configuration Remove TEST_ANALYTICS environment variable handling	vitest.config.ts
Add SonarCloud configuration file	Configure project key and organization Set LCOV report path Set ESLint report path	sonar-project.properties
Update project configuration and documentation	Add ESLint JSON report script Remove Codecov badge from README Retain SonarCloud quality gate badge	package.json README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @hckhanh - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[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