…6281)

## Description
<!---Describe your changes in detail-->
For developer + codebase life improvements, adding ESLint with prettier,
react + react hooks, and flow plugins.

## Motivation and Context
<!---Why is this change required? What problem does it solve?-->
<!---If it fixes an open issue, please link to the issue here.-->
* Improve the code quality and consistency, improves developer QOL
* Implements feature mentioned in
#21062 (comment)

## Impact
<!---Describe any public API or user-facing feature change or any
performance impact-->
* There will be a large number of line changes once all files are
linted, but no functional impact.
> Note: All lint rules are up for discussion if folks on the project
have strong feelings about tab spacing, semicolons, etc. This mostly
implements the "recommended" rules for react, hooks, prettier
formatting, and flow
* Only impacts dev dependencies
* Adds commands to package.json to lint, lint+fix, format, format+fix

## Follow up
1. Add ESLint + prettier config/packages (this PR)
2. Format all UI files, add eslint to CI build process
3. Convert flow -> typescript, add typescript-eslint, remove flow eslint
plugins

## Test Plan
<!---Please fill in how you tested your change-->
For now this simply adds the dependencies, and implements an
eslint/prettier configuration that works. No files have been linted or
formatted yet. I plan to do this in a follow up to keep this PR
manageable, first draft of linting all files here:
#25726

Test the eslint config by running `yarn run lint` for eslint changes, or
`yarn run format` for just prettier formatting changes

## Contributor checklist

- [x] Please make sure your submission complies with our [contributing
guide](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md),
in particular [code
style](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md#code-style)
and [commit
standards](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md#commit-standards).
- [x] PR description addresses the issue accurately and concisely. If
the change is non-trivial, a GitHub Issue is referenced.
- [ ] Documented new properties (with its default value), SQL syntax,
functions, or other functionality.
- [ ] If release notes are required, they follow the [release notes
guidelines](https://github.com/prestodb/presto/wiki/Release-Notes-Guidelines).
- [ ] Adequate tests were added if applicable.
- [ ] CI passed.

## Release Notes
Please follow [release notes
guidelines](https://github.com/prestodb/presto/wiki/Release-Notes-Guidelines)
and fill in the release notes below.

```
== NO RELEASE NOTE ==
```