Improve categorization of features

[rytilahti]

This will update the categorization of features as discussed in the now-obsolete #879:

• Primary: primary controls (state, brightness, etc.) & sensors (like temperature, emeter)
• Config: secondary controls, entity_category=Config
• Info: diagnostic information that is enabled per default in homeassistant
• Debug: diagnostic information that is disabled per default

The id is also made mandatory for features, which will allow using it as a translation key without fear of breaking the "API" inadvertently.

[codecov]

Codecov Report

Attention: Patch coverage is 60.00000% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 90.39%. Comparing base (50b5107) to head (f8eb28f).

Files	Patch %	Lines
kasa/module.py	50.00%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #904      +/-   ##
==========================================
- Coverage   90.40%   90.39%   -0.01%     
==========================================
  Files          70       70              
  Lines        4941     4937       -4     
  Branches     1220     1219       -1     
==========================================
- Hits         4467     4463       -4     
  Misses        384      384              
  Partials       90       90              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sdb9696]

Looks good, there's a lot of changes across files here so I think we should get this merged asap to avoid merge conflicts. Two questions we can address subsequently are:

1. Should we make category a required parameter that must be explicitly set. It's being set on so many features now this shouldn't be too onerous.
2. Should we have some mechanism for indicating the type of data in sensors, e.g. timestamps, so we can derive more sensor classes in HA. Maybe this could be added to unit as seconds etc.

[rytilahti]

Should we make category a required parameter that must be explicitly set. It's being set on so many features now this shouldn't be too onerous.

Yeah, we should probably require explicit setting for category and type, and remove the magic from __post_init__ altogether. Explicit > implicit.

Should we have some mechanism for indicating the type of data in sensors, e.g. timestamps, so we can derive more sensor classes in HA. Maybe this could be added to unit as seconds etc.

Worth considering, but it probably should probably be explicit and separate from the unit. As we are still going to need have some static mapping inside the HA integration, it's not that crucial to have this.