feat: Listen to 202 status

[nhoening]

The client now will react to all 202 responses and poll properly.

• The client's response handling handles 202, meaning to poll once more. Also if maximal polling steps have passed, raise
• add test for get_schedule() to see that all job states are recognized and polled correctly.
• simplify get_schedule() as it was implemeting its own 202 polling (which went against the architecture idea of the client)

Closes #213 (the main purpose there is to listen to 202 status from the server's get_schedule endpoint)

[coveralls]

Coverage Report for CI Build 27339519955

Coverage increased (+0.4%) to 96.591%

Details

• Coverage increased (+0.4%) from the base build.
• Patch coverage: 1 uncovered change across 1 file (18 of 19 lines covered, 94.74%).
• No coverage regressions found.

Uncovered Changes

File	Changed	Covered	%
src/flexmeasures_client/client.py	8	7	87.5%
Total (2 files)	19	18	94.74%

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	704
Covered Lines:	680
Line Coverage:	96.59%
Coverage Strength:	5.8 hits per line

---

💛 - Coveralls