Feature : Standardize the Pull Request GitHub Action to match Talawa API

[aialok]

What kind of change does this PR introduce?

• This pull request standardizes TypeScript GitHub Action workflows by introducing two dedicated jobs: Code-Quality-Checks and Test-Application. The Code-Quality-Checks job handles performing linting, formatting checks and type-error check while the Test-Application job, reliant on the former, focuses on testing the application. This change enhances workflow organization, promoting clear separation of code quality and testing concerns for improved maintainability.

Issue Number:

Fixes #1277

Did you add tests for your changes?

• No

Snapshots/Videos:

If relevant, did you update the documentation?

Summary

• This PR standardizes TypeScript workflows with two jobs: Code-Quality-Checks for linting, formatting, and package installation, and Test-Application for testing. The separation enhances workflow clarity and maintainability.

Does this PR introduce a breaking change?

• No

Other information

Have you read the contributing guide?

• Yes

[github-actions]

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if these conditions occur:

1. The overall code coverage drops below the target threshold of the repository
2. Any file in the pull request has code coverage levels below the repository threshold
3. Merge conflicts

The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

Reviewers

When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

1. comments in this PR or
2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

1. arbitrators of future discussions with other contributors about the validity of your changes
2. point of contact for evaluating the validity of your work
3. person who verifies matching issues by others that should be closed.
4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

1. PRs with issues not assigned to you will be closed by the reviewer
2. Fix the first comment in the PR so that each issue listed automatically closes

Other

1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
2. Read the CONTRIBUTING.md file make

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (0e9e341) 96.23% compared to head (4d59bcf) 96.23%.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #1288   +/-   ##
========================================
  Coverage    96.23%   96.23%           
========================================
  Files          137      137           
  Lines         3344     3344           
  Branches       939      939           
========================================
  Hits          3218     3218           
  Misses         120      120           
  Partials         6        6           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.