Allow storing temperature/humidity entities on an area

[balloob]

Breaking change

Proposed change

Update the edit area dialog to allow storing temperature/humidity sensors on an area. Limits entities to the ones contained in the area.

Backend is already merged

• Add temperature and humidity entities to area registry core#135423

(There are a lot of cool things that we can do with this, including dashboard strategies, showing this data on area info page and what not. That's for other PRs by other people :) )

Type of change

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

Example configuration

Additional information

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

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• 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

[piitaya]

I think we can consider splitting these settings because it become too big.
Also, we should explain to the user where these entities will be used (dashboard, voice, etc...)
Code wise, it is ok for me 🙂

Note : We should add an area and a device parameter to the entity-picker/entity-selector so we don't need to build a specific filter for that.