Enable local_partial_types for strict typing [mypy]

[cdce8p]

Proposed change

At some point local_partial_types will be enabled by default for mypy.
Start by enabling it as part of the strict typing settings.

From the mypy docs:

In mypy, the most common cases for partial types are variables initialized using None, but without explicit Optional annotations. By default, mypy won’t check partial types spanning module top level or class top level. This flag changes the behavior to only allow partial types at local level, therefore it disallows inferring variable type for None from two assignments in different scopes. For example:

from typing import Optional

a = None  # Need type annotation here if using --local-partial-types
b: Optional[int] = None

class Foo:
    bar = None  # Need type annotation here if using --local-partial-types
    baz: Optional[int] = None

    def __init__(self) -> None:
        self.bar = 1

reveal_type(Foo().bar)  # Union[int, None] without --local-partial-types

Note: this option is always implicitly enabled in mypy daemon and will become enabled by default for mypy in a future release.

https://mypy.readthedocs.io/en/stable/command_line.html#cmdoption-mypy-local-partial-types

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

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

• Documentation added/updated for www.home-assistant.io

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

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[cdce8p]

The mypy issue will be fixed with the next version which hopefully gets released this week 🤞🏻

I could work around it, but that doesn't seem worthwhile. Final like I added in #86410 should be enough. Let's wait for the mypy release.

homeassistant/components/logbook/queries/common.py:38: error:
    Need type annotation for "PSUEDO_EVENT_STATE_CHANGED" (hint: "PSUEDO_EVENT_STATE_CHANGED: <type> | None = ...")  [var-annotated]

core/homeassistant/components/logbook/queries/common.py

Line 38 in a1a324a

PSUEDO_EVENT_STATE_CHANGED: Final = None