* replace attrs to defaultProps (#20260)

* replace attrs to defaultProps

* fix replaced attrs

* fix className in defaultProps

* use emotion (#20265)

* replace attrs to defaultProps

* fix replaced attrs

* use emotion

* fix typo in css

* eliminate innerRefs

* fixes

* fixes

* fixes

* fixes

* flakes

* specs

* specs

* docs

* specs

* fix last spec

* remove classNames from defaultProps

Overall purpose of PR is to add row drill-ins to the tools to fix broken questions, so you can take a look-see into what the broken questions are.

A tiny nit thing wasn't caught by CI and broke master. This was because there's a CI cache. I can confirm that this didn't hit the CI cache and the other thing that broke isn't breaking anymore

This reverts commit f94510a3.

Details page for tools to fix broken questions. Also the PR ran long enough that nemanja found some bugs in the details page. Does not include any loading overlay or anything to indicate that reloads are happening, which is for 41.1 I guess

* grammar and microcopy tweaks

* update cypress test

* fix another test

* update test again

* subscriptions and alerts audit

* Add tables

* Add tables

* Extract to lib

* Extract to lib

* Add modal

* Add modal

* Add modal

* Fix modals

* Fix modals

* Add children for displaying modals

* Add children for displaying modals

* Add children for displaying modals

* Add children for displaying modals

* Add edit dialogs

* Add edit dialogs

* Add edit dialogs

* Add edit dialogs

* Remove deletion

* Remove deletion

* Add users

* Add users

* Fix selection issues

* Add placeholder

* Add placeholder

* Add delete button

* Fix wrapping issues

* F

* Small fixes

* Add reloading

* fixes

* cypress specs

* fixes

* post rebase fixes

* rebase fixes

* review fixes

Co-authored-by: Alexander Polyankin <alexander.polyankin@metabase.com>

Tools are there. Modal is not, along with some styling, but BE has been languishing for months so I wanted to get this in

Peeps want to make questions faster, but we don't give the data about query execution in a very user-friendly way. Here's it in a user-friendly way.

Co-authored-by: Alexander Lesnenko <alxnddr@users.noreply.github.com>

* Switch the rule to "error"

* Disable linting for `prop-types` in unit tests

* Disable linting for `prop-types` in all affected files

* yarn remove flow-bin eslint-plugin-flowtype

* CI: remove fe-linter-flow

* Remove Flow from ESLint config

* Remove Flow type annotations and directives

* Simplify Flow types for React elements and components

* Import missing Flow types

* Remove lint-flow from package.json