Allow zone to be a polygon

[Misiu]

Breaking change

None, the change is backward compatible, so the user will be able to decide if he wants a circular zone (the default) or a polygon zone.

Proposed change

This PR adds support for creating zones based on polygons.
The code is based on https://github.com/Baael/polygon-zone
The idea was proposed in WTH: https://community.home-assistant.io/t/wth-we-only-have-round-shaped-zones/468137/1
The solution is using shapely, but I'm not sure if it will work everywhere, because I found two opinions:
home-assistant/architecture#954 (reply in thread)
home-assistant/architecture#954 (reply in thread)

I've used the ray-casting algorithm from https://www.youtube.com/watch?v=RSXM9bgqxJM.

I'd like to get feedback about this approach before I move to frontend and documentation.

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
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format 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.

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (zone) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zone can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign zone Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[MartinHjelmare]

This change requires an architecture discussion.

https://developers.home-assistant.io/docs/core/entity#changing-the-entity-model

[Misiu]

I'll create a discussion then. Let's leave this as a draft until a decision is made.

[frenck]

Let's close it until it is approved.

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[joostlek]

@Misiu, check your discord, made a thread in the HA discord for discussing polygon stuff