v1.2.2

Bug Fixes

Entities still becoming unavailable after ~2 hours (#81)

The fix shipped in v1.2.1 did not fully resolve the issue. While the library
attempted to strip the server-supplied expiry from the coulomb_sess cookie on
every response, aiohttp tracks cookie expiry in a separate internal data structure
from the cookie value itself. Calling update_cookies() without a max-age updates
the stored value but leaves the original expiry timestamp untouched, so the cookie
was still evicted after two hours regardless.

This is resolved in python-chargepoint 2.3.2, which sets an explicit long-lived
max-age when re-seeding the cookie, causing aiohttp to properly overwrite the
expiry timestamp.