Add base ESLint config

[mcous]

This PR adds base ESLint config. I didn't add any rules, just base extensions. Could use help selecting more rules for this PR!

[DTCurrie]

✅ pending decision on explicit rule setting

[mcous]

I did my best to incorporate the app's ESLint config into the base config here. Intentional deviations from the app's explicit and/or effective config:

Things that were explicitly errors and are now off

• array-element-newline - Handled by prettier
• dot-location - Handled by prettier
• function-call-argument-newline - Handled by prettier
• function-paren-newline - Handled by prettier
• implicit-arrow-linebreak - Handled by prettier
• max-len - Handled by prettier
• multiline-ternary - Handled by prettier
• object-curly-spacing - Handled by prettier
• object-property-newline - Handled by prettier
• no-multiple-empty-lines - Handled by prettier
• quotes - Handled by prettier
• semi - Handled by prettier
• comma-dangle - Handled by prettier
• quote-props - Handled by prettier
• no-return-await - Replaced by more accurate @typescript-eslint/return-await
• require-await - Replaced by more accurate @typescript-eslint/require-await
• unicorn/no-unsafe-regex - Not currently recommended by unicorn
  • See The no-unsafe-regex rule is annoying sindresorhus/eslint-plugin-unicorn#153
• unicorn/import-index - Deprecated by unicorn
  • https://github.com/sindresorhus/eslint-plugin-unicorn/blob/main/docs/deprecated-rules.md#import-index
• unicorn/prefer-object-has-own - Replaced by prefer-object-has-own
• unicorn/string-content - Needs an explicit configuration to do anything
  • See https://github.com/sindresorhus/eslint-plugin-unicorn/blob/main/docs/rules/string-content.md
• @typescript-eslint/indent - Prettier

Things that were implicitly errors via eslint:all and are now off

• block-scoped-vars - Unnecessary because we don't allow var
• complexity - Redundant with sonarjs/cognitive-complexity
• consistent-this - We have arrow functions now
• dot-notation - Replaced by @typescript-eslint/dot-notation
• func-name-matching - We have arrow functions now
• id-denylist - Needs an explicit configuration to do anything
• id-match - Needs an explicit configuration to do anything
• no-array-constructor - Redundant with @typescript-eslint/no-array-constructor
• no-empty-function - Redundant with @typescript-eslint/no-empty-function
• no-eq-null - Redundant with eqeqeq
• no-implied-eval - Replaced by @typescript-eslint/no-implied-eval
• no-inline-comments - Redundant with line-comment-position
• no-loss-of-precision - Redundant with @typescript-eslint/no-loss-of-precision
• no-restricted-* - Needs an explicit configuration to do anything
• no-throw-literal - Replaced by @typescript-eslint/no-throw-literal
• no-useless-constructor - Replaced by @typescript-eslint/no-useless-constructor
• sort-vars - We don't only multiple variables initialized in one line

Things that were off and are now errors

• no-undef - Enabled by eslint:recommended
  • According to comments, it was disabled in app due to issues with Vue.
  • I'd like to keep it enabled in the base config and disable in a Vue-specific config, if necessary.
• no-unused-var - Replaced by @typescript-eslint/no-unused-vars, enabled by recommended config
  • Same story
• unicorn/no-empty-file - Enabled by unicorn/recommended and also recommended by me.
  • If we really need an empty file, we can add an override or a comment.
• unicorn/filename-case - Enabled by unicorn/recommended and also recommended by me.
  • I've seen too many people get tripped up by case-sensitive vs case-insensitive filesystems working in JS codebases over the years
  • This rule with its default of kebab-case.ext is good
  • viamrobotics/prime had two inconsistently cased filenames that I saw (and fixed) last week

Things that are no longer explicit, but still enabled from extended recommendations.

• no-unsafe-optional-chaining
• unicorn/import-style
• @typescript-eslint/no-explicit-any
• @typescript-eslint/ban-ts-comment

Other notes

• I extended plugin:@typescript-eslint/strict, which means several rules that were not specified one way or another are now on
• I did not extend and vue rules because I'd like to layer on a Vue-specific config rather than incorporate it into the base.
• Ditto for tailwind
• If a rule is marked as off in the app's config and not mentioned here nor in the base config, it is still off in the effective config, either due to extending a config or by omission (unless I missed something!)

[micheal-parks]

Great stuff here, thank you!