pre-commit: ship default and full configs

[scop]

Description:

Yet another option for tackling mypy in pre-commit. This is my current favorite. I think we should adopt this one instead of #28405, and also add at least pylint here in the future (leaving that out for now, though).

For now, the only difference between the two is mypy.

It's a bummer that we need to duplicate stuff in the default config in the "all" one, filed RFE about that: pre-commit/pre-commit#1203

Related issue (if applicable): fixes #28283 fixes #28405

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

If the code does not interact with devices:

• Tests have been added to verify that the new code works.