chore(Lint): Use oxlint for linting

[gatzjames]

Motivation:
Our current eslint configuration is quite complex which makes it hard to update to the latest version and keep up to date.
There are also times where formatting rules fight each other and saving a file leads to a flash of formatting that creates some very weird indentation results.
Ideally we want our linter to only be concerned about code issues and use a formatter like prettier to handle how our code is formatted.
oxlint is now in beta and already used by some pretty big projects

Highlights:

• Replaces eslint with oxlint
• Added settings and recommended extension for oxlint
• Fixed some issues where we have unused variables and no keys on react lists
• Lint in GitHub actions goes from ~15s to ~0s

Figure out:

• What rules should we enforce per workspace?
• Review and compare overall DX compared to eslint

[CurryYangxx]

What is our motivation for replacing eslint with oxlint?
oxlint doesn't seem to have a major release yet, and I'm worried that it's not stable enough for us.
I suggest waiting until it releases a major version and is verified by more people before deciding whether to use it.

[jackkav]

I agree with @CurryYangxx, especially as they are still working on an unreleased formatter. Keep the branch around though and we can revisit on their 1.0 release