Code Quality: enable a few useful ESLint rules

[swissspidy]

Context

Related to #12086

Summary

While the solutions mentioned on that ticket are a bit outdated and not super useful for us, I was able to steal a couple of useful ESLint rules from them for our project.

Relevant Technical Choices

To-do

User-facing changes

Testing Instructions

• This is a non-user-facing change and requires no QA

This PR can be tested by following these steps:

Reviews

Does this PR have a security-related impact?

No

Does this PR change what data or activity we track or use?

No

Does this PR have a legal-related impact?

No

Checklist

• This PR addresses an existing issue and I have linked this PR to it in ZenHub
• I have tested this code to the best of my abilities
• I have verified accessibility to the best of my abilities (docs)
• I have verified i18n and l10n (translation, right-to-left layout) to the best of my abilities
• This code is covered by automated tests (unit, integration, and/or e2e) to verify it works as intended (docs)
• I have added documentation where necessary
• I have added a matching Type: XYZ label to the PR

---

Fixes #

[googleforcreators-bot]

Plugin builds for bcc4530 are ready 🛎️!

• Download development build
• Download production build

[miina]

Looks like unit tests are failing now on this PR.