fix(client): raise `InvalidToken` if the token expires while using `lock()`

[palazzem]

Related Issues

• Related to https://github.com/palazzem/ha-econnect-alarm/issues/117

Proposed Changes:

lock() method uses the @contextmanager decorator that doesn't propagate inner exception. If a 401 response is received (the token is expired), that error is not propagated above and it causes the token to not get refreshed until the next poll(). In a real scenario where you have delays, it means it's very likely that you can't interact with the system unless you hit the exact window between one refresh and another.

Testing:

Acquire a token, let it expire, call lock()

Extra Notes (optional):

n/a

Checklist

• [x] Related issues and proposed changes are filled
• [x] Tests are defining the correct and expected behavior
• [x] Code is well-documented via docstrings

[coveralls]

Pull Request Test Coverage Report for Build 7278102786

• 2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 7115497080:	0.0%
Covered Lines:	392
Relevant Lines:	392

---

💛 - Coveralls