Pyemvue

Some Python types weren't being reported or were inconsistent. Fixed the ones I noticed.

- Add Breaker PIN support for EVSE. If a Breaker PIN is set it will be passed on update requests.
- v0.17.0 added endpoints for updating some settings on channels, such as name, and getting the channel types.
- v0.17.0 also forced usernames to be lowercase no matter what casing they're provided.

- Added `get_devices_status` function to replace `get_outlets` and `get_chargers`. Returns both sets in one API call and can update the `connected` state of devices. The older methods still exist but will be removed in the future.
- Merged PR 36 to set a default timeout on requests. Defaults at 6 seconds for connects and 10 seconds for reads.
- Added typing hints for all functions and a number of variables.
- Updated a few of the test scripts. `outlet_test.py` will also print out EV chargers. Running the module directly should properly print out the access token and will now print out the state of any outlets or EV chargers. Both files now take advantage of the typing hints as well.

This release refactors the authentication to be more in line with what Home Assistant expects for managing tokens and replaces the use of warrant with pycognito. The automatic storing of tokens has also changed to use "username" and underscores for things like "id_token". This also fixes the parsing issue in 30.

Due to backing API updates the get_devices_usage method has been replaced with get_device_list_usage which takes the same parameters but has a very different return. See the updated documentation in the readme for an example of how to get all the data out of this call, but the main thing to keep in mind is that the devices/channels are now nested.

This release adds support for controlling EVSEs/EV Chargers. You can start and stop charging, as well as set the desired and maximum charge rates for the EVSE. Additionally there's a method to check if the API is down for maintenance and several objects were updated to include more of the information that is returned from the API, most notably latitude and longitude is populated where available, information about if the device is connected and when it went offline, and the parent device id/channel for nested devices.