just a small .eslintrc change

[cirex-web]

• Changed eslint prettier errors to warnings
• Followed https://github.com/prettier/eslint-plugin-prettier#recommended-configuration on how to set up eslint-plugin-prettier

[GhostOf0days]

I thought about this, and I'm opposed to this change. I'm not sure where we will run into conflicts between Airbnb and recommended Prettier configs. In all honesty, Airbnb standards are better. In general, Airbnb engineers are very good at making TypeScript tools (such as https://github.com/airbnb/ts-migrate) and standards. I would consider Airbnb the gold standard for TypeScript and relevant code standards similar to how Google's C++ Style Guide is the gold standard for C++ code.

As for the errors to warnings, this would make sense if we didn't have a GitHub Action for linting and making sure we follow code standards, but we do, so it should be kept how it previously was. The reason is, when linting, warnings would not result in failure, so the GitHub Action could show a green checkmark on GitHub when a PR is made although it should fail tests. This issue is seen when installing npm packages in the process of running a GitHub Action. Warnings are ignored and could cause us to merge in packages that have security vulnerabilities or are deprecated (we currently take care of this through Dependabot scans to create automatic PRs).