chore: eslint cleanup and code changes accordingly

[BlankParticle]

What does this PR do?

Setup Eslint properly in the Project and make code changes accordingly.
Please don't merge until the open PRs are merged and this branch is rebased on them

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Chore (refactoring code, technical debt, workflow improvements)
• Enhancement (small improvements)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist

Required

• Read Contributing Guide
• Self-reviewed my own code
• Tested my code in a local environment
• Commented on my code in hard-to-understand areas
• Checked for warnings, there are none
• Removed all console.logs
• Merged the latest changes from main onto my branch with git pull origin main
• My changes don't cause any responsiveness issues

Appreciated

• If a UI change was made: Added a screen recording or screenshots to this PR
• Updated the UnInbox Docs if changes were necessary

[BlankParticle]

• chore: load opentelemetry modules on demand #619
• chore: remove unused routes and checks #618
• chore: eslint cleanup and code changes accordingly #586 👈
• feat: fixing every little annoying issue #617
• feat: new security page and workflow #615
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @BlankParticle and the rest of your teammates on Graphite

[CLAassistant]

All committers have signed the CLA.

[BlankParticle]

Merge activity

• Jul 28, 11:09 AM EDT: @BlankParticle merged this pull request with Graphite.