We need to setup pre-commit. This PR also addresses the resulting violations.
### Acceptance Criteria
- [ ] `pre-commit` is configured with built-in hooks that are used in other adapter repos
- [ ] `pre-commit` is configured to run `black`, `flake8`, and `mypy` using the configurations in `pyproject.toml`
- [ ] `pre-commit` can be installed via `hatch`
- [ ] GHA workflows that run code quality checks, or use `pre-commit` in other ways (e.g. to tidy up the changelog on release) are updated so they work properly
### Tasks
- [x] Add `pre-commit` as a dev dependency
- [x] Add a `.pre-commit-config.yaml` file that uses the `local` repo so that the config in `pyproject.toml` gets used everywhere
- [x] Add a command `hatch run dev` that will instantiate the dev environment and install `pre-commit` hooks
- [x] Combine `default`, `lint`, and `typecheck` `hatch` environments into the `hatch` `default` environment
- [x] Update `code-quality` workflow to run all code quality at once instead of as separate steps
- [x] Run `pre-commit` (by running `hatch run code-quality`) to trigger updates so that CI passes
- [x] Remove offending tests that don't pass code-quality, but which also don't belong in `dbt-postgres` and which belong in `dbt-core` instead
[x] I have run this code in development, and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc.) or this PR has already received feedback and approval from Product or DX
Problem / Solution
We need to setup
pre-commit
. This PR also addresses the resulting violations.Checklist