Update eslint rules

[toasted-nutbread]

This change turns on a few rules:

• no-octal - this was inadvertently set to off, no changes were required.
• no-octal-escape - this was inadvertently set to off, no changes were required.
• @typescript-eslint/no-redundant-type-constituents - enabled this, only had one issue to resolve in a type file.
• @typescript-eslint/no-floating-promises - this is the big one, requires either await or void for async functions. This should help prevent issues where sync functions are subsequently changed to async, or just situations where someone might forget. It makes the intent required to be more explicit. Unfortunately, there were about 300 places in the code that needed this to be addressed. Most of which were turned to void, which is the existing behaviour, and only a few were changed to await.

[github-actions]

✔️ No visual differences introduced by this PR.

View Playwright Report (note: open the "playwright-report" artifact)

[djahandarie]

Wonderful! I had to turn on no-floating-promises for the files I was working in when I was doing my performance-batching changes at it was simply too hard to do a sync->async refactor without it. This is great to have.