Fix Code Coverage GitHub Action Test for Values > 0%

[palisadoes]

Describe the bug

1. We are migrating from jest to vitest for our test suite
2. We had to modify our GitHub Actions workflow to calculate the total code coverage from both suites (See screenshots below)
3. The Very Good Coverage check now fails for any value set > 0
   1. https://github.com/VeryGoodOpenSource/very_good_coverage
4. We need to be able to set this value to the 90% overall code coverage for the repo.
5. Checks need to fail if either the PR code patch or the overall repo's code coverage falls below this threshold
6. The GitHub action file can be found here:
   1. https://github.com/PalisadoesFoundation/talawa-admin/blob/develop-postgres/.github/workflows/pull-request.yml

To Reproduce
Here is an example of a failing test suite when the threshold value was set to 89%

• https://github.com/PalisadoesFoundation/talawa-admin/actions/runs/12844104521/job/35816780243

Expected behavior

• See above

Actual behavior

• See above

Screenshots

1. Merging of the code coverage files from jest and vitest
   

2. The failing check section. Failures only happen when not set to zero
   

Additional details
Add any other context or screenshots about the feature request here.

Potential internship candidates

Please read this if you are planning to apply for a Palisadoes Foundation internship

• Student Internship Programs talawa#359

[palisadoes]

@varshith257

[varshith257]

I am thinking once all jest files are converted to vitest, we can re-enable it by remove those all flags introduced

Let's put priority on that refactor issues and Prs and close them ASAP

[palisadoes]

I'll assign it to you so we don't forget

How far away are we from completing the vitest conversion?

[varshith257]

I think only 3-4 issues left

[palisadoes]

You should take them over and complete them if there is no response.