M2-4835: Linting rules for mindlogger-admin

[sultanofcardio]

resolves: M2-4835

This PR creates a GitHub Action to run linting tasks on pull requests submitted to the repository. As part of the ticket, I took the opportunity to update the ESlint rules on the project. These updates have raised a number of linting issues, but won't block the merging of pull requests. While I've addressed some of the smaller items (and any error ones), I expect that these will be addressed in the normal course of feature development so that we can eventually require linting checks to pass in order to merge PRs.

Here's a summary of what changed:

Conflicting ESLint configurations

There are currently two ESLint configurations in the project:

• An eslintConfig property in the package.json file
• A .eslintrc file

ESLint documentation says that only one of these is read, and the .eslintrc takes precedence. Thus, I've removed the ignored configuration since it wasn't being used.

Prettier Code Formatting

Prettier has been configured in the project as the code formatter of choice, but it is currently conflicting with a number of code formatting ESLint rules. The prettier ESLint plugin disables these rules if it is placed as an inherited configuration at the end of the extends array, so I have made this change. The prettier ESLint plugin also enables Prettier as an ESLint rule, so that code formatting issues become errors. This should be okay, since Prettier fixes them for you.

In addition, I've disabled/removed some other code formatting related rules that aren't explicitly handled by the Prettier plugin. These include:

• padding-line-between-statements
• no-extra-semi
• jsx-quotes - I've moved this one to the Prettier config with jsxSingleQuote

Opinionated changes

There are a number of other changes I've made that I think will allow for improved code quality. These are:

• Turning on the react-hooks/exhaustive-deps rule
• Adding the unused-imports ESLint plugin
• Turning on the @typescript-eslint/no-non-null-assertion rule

[aws-amplify-us-east-2]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-1472.dpmzgfnfrj2mv.amplifyapp.com

[IhorNesterenko99]

I've noticed that the unit tests are failing after the changes made in the pull request. Could you please take a look and correct any issues with the unit tests?

Additionally, there are some conflicts that need to be resolved before this pull request can be merged. Could you please review and resolve the conflicts accordingly?

[sultanofcardio]

I've noticed that the unit tests are failing after the changes made in the pull request. Could you please take a look and correct any issues with the unit tests?

Additionally, there are some conflicts that need to be resolved before this pull request can be merged. Could you please review and resolve the conflicts accordingly?

@IhorNesterenko99 Yes, I will address these. I initially believed that the tests were failing because of this commit, but after rebasing again I realised they are still failing.

[IhorNesterenko99]

I wanted to bring to your attention that our Jenkins continuous integration is currently failing. Here's a screenshot for reference:

It might be a good idea to reach out to our DevOps lead, Raman Siauko, to investigate what might have caused this issue.

[alex-i-e]

Perfect! You've added meaningful and valuable lint rules for ongoing on project, some of them will point on places that should be fixed in future. I appreciate your input and contribution to improving quality!