ci: add codecov integration

[brionmario]

Purpose

This pull request introduces comprehensive code coverage reporting across multiple packages and standardizes the test coverage configuration. The main improvements include adding Codecov integration to the CI workflow, configuring Istanbul as the coverage provider for all relevant packages, and updating dependencies to use a centralized version management approach via the pnpm workspace catalog.

CI/CD and Code Coverage Integration:

• Added a new codecov.yml configuration file to enforce minimum coverage thresholds (50%) for all major packages and to enable Codecov comments on pull requests.
• Updated .github/workflows/pr-builder.yml to upload coverage reports for each package to Codecov after running tests, ensuring each package's coverage is tracked independently. Also, added concurrency control to prevent duplicate builds for the same PR. [1] [2]

Testing and Coverage Configuration:

• Standardized all vitest.config.ts files across packages to use Istanbul as the coverage provider, ensuring consistent coverage reporting. [1] [2] [3] [4] [5] [6]
• Updated the test script in packages/vue/package.json to use the default vitest command, simplifying test execution.

Dependency Management:

• Updated all relevant package.json files to source vitest, @vitest/browser, and @vitest/coverage-istanbul from the pnpm workspace catalog, ensuring consistent versions across packages. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13]
• Added new entries for vitest, @vitest/browser, and @vitest/coverage-istanbul to the pnpm-workspace.yaml catalog for centralized dependency management.

Miscellaneous:

• Minor cleanup in packages/vue/tsconfig.eslint.json to adjust included files for linting.
• Moved and updated the Vue package's vitest.config.ts for consistency and maintainability.

These changes collectively ensure robust, consistent, and visible test coverage reporting across the codebase, improving code quality and maintainability.

Related Issues

• Fixes ci: add unit test coverage support #185

Related PRs

• N/A

Checklist

• e2e cypress tests locally verified.
• Manual test round performed and verified.
• UX/UI review done on the final implementation.
• Documentation provided. (Add links if there are any)
• Unit tests provided. (Add links if there are any)
• Integration tests provided. (Add links if there are any)

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines?
• Ran FindSecurityBugs plugin and verified report?
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets?