Add GitHub Action for linting, testing, and building TypeScript project

[smog-root]

Closes #126

CI_LINT.yaml :

Working PROOF :
It show's what are the errors in files ⬇

This PR introduces a comprehensive Continuous Integration (CI) workflow using GitHub Actions to automate the following tasks for the TypeScript project:

• Linting: Ensures that the code follows the defined style and best practices.
• Testing: Runs the project’s test suite to validate code functionality.
• Building: Compiles the TypeScript code to ensure there are no type errors and generates the final JavaScript output.

Details of Workflow:

Trigger Conditions:

The workflow will automatically trigger on:

• Push events to the main branch.
• Pull requests targeting the main branch.

Jobs:

Linting (ESLint):

• Lints all TypeScript files (.ts and .tsx) in the project using ESLint.
• This ensures that all code adheres to the project's coding standards and best practices.

Building (TypeScript Compiler):

• Compiles the TypeScript code using the TypeScript compiler (tsc) to check for any type errors and ensure that the project builds successfully.
• The compiled output is stored in the dist directory (as specified in tsconfig.json).

Testing (Jest):

• Runs the test suite using Jest to validate that the code behaves as expected.
• Ensures that no new changes break existing functionality.

Steps Performed in the Workflow:

• Checkout the code from the repository using actions/checkout@v3.
• Set up Node.js using actions/setup-node@v3 with the specified Node.js version (16.x).
• Install dependencies via npm install.
• Run ESLint to check for linting issues using npm run lint.
• Compile TypeScript code using npm run build.
• Run Jest tests using npm test.

---

pr-checker.yaml :

Usage:

1. When a pull request is created or edited, the workflow automatically triggers.

2. The workflow checks for:

• A non-empty PR description.
• A valid issue reference format (Fixes , Close, Closes, Closed , Fix , Fixed , Resolve , Resolves #Issue_number).

3. If either check fails, the PR will be marked as failing, and the author will receive clear error messages in the PR comments.
4. If all checks pass, a confirmation message will indicate that the PR is valid.

Note: Kindly add all the labels added to the issue, to this PR!

@ratnesh-maurya

[smog-root]

Upgrade it to level3. It deserves it! @ratnesh-maurya

[ratnesh-maurya]

Will review Tomorrow