[TICKET-PR] Code linting and formatting setup: ESlint + Prettier

[Ifycode]

This pull request makes the following changes

• Fixes Code linting and formatting setup: ESlint + Prettier tickets-ready-for-fixing#16

General checklist

• My pull request adheres to the community pull request guidelines.
• I have read and understood the Pull request guideline extension section found at the bottom of this pull request description/body.
• I have replaced the dummy text under the subheading Testing checklist below with the testing checklist from the issue ticket I'm working on.

Testing checklist

• Eslint code quality-related rules have been setup:
  • console.log usage (warning)
  • Unused variables (error)
  • Inconsistent variable or function naming styles (default: camelCase, otherwise give error)
• Prettier code formatting-related settings have been setup - In addition to prettier's default settings:
  • Use 2 spaces for indentation (instead of tabs)
  • Use single quote for strings
  • Add trailing comma to the last item in an object
  • End every single code statement with a semicolon
  • Ensure that every file ends with exactly one empty line
• These all work in the setup library.
• Devs are able to to import and use the rules from their nodejs-based project.
• Detailed user and contributor documentation are included.
• I certify that I ran my checklist.

How to run project

Find detailed installation guide in the docs.contributors/README.md file of this branch & pull request.

Pull request guideline extension

Note

Do not remove this note or section. This talks about extra things to take note of, in addition to the directions given in the community pull request guidelines.

We appreciate the time taken to help tackle issue tickets our community. Please go ahead to submit your pull request even if it is not yet completed, and push to the pull request actively. This will allow us to know that you have not abandoned the issue ticket. However, you should only alert reviewers about your pull request as explained below, to avoid flooding their GitHub notifications unnecessarily.

"Ready for review" implies that things are working as expected, according to how it is specified in the issue ticket you are working on. Ensure that you test the code that you are working on, that it works as expected. Don't just request for review when your pull request is not yet done and working.

The only time you should be making people review something incomplete is: if you want to show them what's not working, so that they can send help or guidance. If this is the case, be explicit about this in our Discord community or in the comment of your pull request (after you have submitted the pull request).