refactor(deps): migrate from archived `tslint` to `eslint`

[agilgur5]

Fixes #264 Supersedes #265 and #428, as well as part of #432 (the node-version-file part in the GH Actions) Closes #265, Closes #428

Credit very much given to the original author of those who put in most of the legwork @sosukesuzuki, I am just updating it to get it to pass CI etc

Motivation

• tslint had been officially deprecated in favor of eslint with @typescript-eslint since at least early 2019
  • it's been completely archived since at least mid-2021 as well

Config partly mostly double-checked against other tslint -> eslint migrations I've worked on recently: https://github.com/argoproj/argo-workflows/pull/12163 and https://github.com/ezolenko/rollup-plugin-typescript2/pull/463

• Did not fully check the Storybook overrides, but it did LGTM in code review of #265. Per https://github.com/argoproj/argo-ui/pull/265#pullrequestreview-1581209971, can make further changes as needed after this PR is merged

Modifications

Migration changes

• migrate lint script to use eslint
• migrate tslint & tslint-react to their eslint / @typescript-eslint counterparts
• migrate tslint.json to .eslintrc.json
  • more or less the same configuration with same plugins
  • use recommended rulesets
  • globally disable @typescript-eslint/no-explicit-any and @typescript-eslint/no-non-null-assertion
  • these are commonly disabled as both of these are already explicit typings (as opposed to implicit ones, which we should check for)
    • there are valid uses of these two, and while they can be misused, that's somewhat uncommon (in my experience)
  • consistent with Argo Workflows's configuration in https://github.com/argoproj/argo-workflows/pull/12163
• migrate tslint:disable-next-line comment to eslint-disable-next-line comment

Other necessary or related changes

• remove unused jshintrc

• fix various lint errors

  • remove various unused arguments
  • add various missing props
  • {} -> any or a more specific type
  • add UNSAFE_ prefix to deprecated React methods
  • minor automated style changes

• upgrade Node version to latest v14 so that install & CI passes with current versions of deps (they require newer Node)

  • note that Node v14 is EoL and has been since April 2023
  • but, per https://github.com/argoproj/argo-ui/pull/265#issuecomment-1684181071 and https://github.com/argoproj/argo-ui/pull/432#issuecomment-1879767403, this is the least intrusive update for now that gets build passing
  • will further update node in a separate PR

Verification

CI passes