Integrating JShint into our Workflow

[khalifat3]

This pull request finalizes the integration of JSHint into our development workflow. The integration includes adjustments to our package.json, the addition of JSHint configuration files, and updates to our GitHub Actions to incorporate JSHint checks. This ensures that our code adheres to our specified coding standards automatically before merges.

• Adding JSHint to scripts in package.json:
  Modified the scripts section to include a JSHint run command, allowing developers to execute lint checks manually.

• Added and populated .jshintignore & .jshintrc:
  .jshintignore: Specified files and directories that JSHint should ignore during its run.
  .jshintrc: Defined a set of linting rules tailored to our project's coding standards to ensure consistency.

• Trying to Integrate JSHint into our GitHub workflow:
  Updated our GitHub Actions configuration to try and run JSHint checks on pushes and pull requests to the f24 branch. This is crucial for catching issues early and ensuring that only code that meets our quality standards is merged. This does not function correctly in this PR even though we did add the jshint.yaml, but we fixed it in Fixing the jshint.yaml to Run as Part of Workflows #48.

[coveralls]

Pull Request Test Coverage Report for Build 11589677579

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 30 of 33 (90.91%) changed or added relevant lines in 22 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage decreased (-0.006%) to 82.686%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/meta/configs.js	0	1	0.0%
src/socket.io/categories.js	0	1	0.0%
src/socket.io/modules.js	0	1	0.0%

Files with Coverage Reduction	New Missed Lines	%
src/user/auth.js	1	92.06%

Totals
Change from base Build 11555126436:	-0.006%
Covered Lines:	22351
Relevant Lines:	25612

---

💛 - Coveralls

[Abdallah-Abdaljalil]

We made changes associated with integrating JShint into our workflow and fixing the errors JShint was giving us locally. They passed all the tests here in the PR when we committed our changes, however, we made the mistake of merging instantly instead of adding a reviewer. This is why we created PR #47 to revert the changes done by this PR. I am commenting on this PR to clarify the lack of a review before the merge. I would have said it was fine to merge anyway since I saw that all the tests passed both locally and on GitHub before the merge mistake. We also created PR #48 because we thought it would be safer to create a new branch for any additional changes we need to make. We forgot to modify the jshint.yaml file so that it runs as part of our workflows on GitHub. That's the reason for the extra branch and PR.