Resolving ESLint Issues on the js/ directory and .eslintrc.json for proper linting

[omsuneri]

@walterbender when i tried running npx eslint --debug js (debugging the eslint over js directory)
i figured out many errors and potential warnings related to linting in many of the files

so in this PR i m doing the following things

1. Parser Update: Replaced "babel-eslint" with "@babel/eslint-parser" (since babel-eslint is deprecated).

2. Added "node": true to support GitHub Actions' Node.js runtime.

3. resolving the "quotes", "indent", "quotes" error using npx eslint js --fix to fix some of the issues related to the linting

as a result of doing these changes the errors and warnings related to the eslint are resolved -->

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[omsuneri]

@walterbender when i try resolving the errors i found that the ESLint workflow is running absolutely fine just some thing we need to do to ignore the no-undef error will be resolving that to in this PR only also
the cause of workflow failure is the remaing error of no-undef and some others too
will be resolving soon

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[omsuneri]

@walterbender I resolved all the eslint related issue in the js directory, also in this PR I turned off some of the unrequired rules of ESLint I checked through each and every file and resolve all the possible linting errors and warning and the workflow for ESLint is now working absoutely great please review this !!

[omsuneri]

@walterbender right now our ESLint workflow is working fine as it is able to detect the linting issues on the changed files which our previous workflow is unable to do also as we have many linting issues priorly in the js dir we are unable to detect those but now you can view that in #4551 the linitng workflow is doing its works absolutely great and by merging this PR all the liniting issues of js dir also be resolved and we have a clean code !!

[Ubayed-Bin-Sufian]

@omsuneri I think you were trying to mention #4548.

[omsuneri]

@Ubayed-Bin-Sufian I didn't understand your point

[Ubayed-Bin-Sufian]

@walterbender right now our ESLint workflow is working fine as it is able to detect the linting issues on the changed files which our previous workflow is unable to do also as we have many linting issues priorly in the js dir we are unable to detect those but now you can view that in #4551 the linitng workflow is doing its works absolutely great and by merging this PR all the liniting issues of js dir also be resolved and we have a clean code !!

In this comment, you have mentioned the PR 4551. Maybe you were trying point to #4548.

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.