Fix: Schedule force field dev version

[BelhsanHmida]

Summary

• add a helper for API-generation-style server version checks
• use it in trigger_schedule() when deciding the schedule force-new-job field name
• preserve legacy force_new_job_creation behavior for older sensor endpoint usage
• add regression coverage for both 0.33.0.dev* asset scheduling and older server fallback

Why

0.33.0.dev* compares lower than final 0.33.0 under normal packaging version semantics, but those dev servers can already expose the 0.33 asset scheduling API shape.

Without this, trigger_schedule(..., asset_id=..., prior=...) can send:

"force_new_job_creation": true

to the asset scheduling endpoint, which expects:

"force-new-job-creation": true

and rejects the request with a 422.

Tests

python -m pytest tests/client/test_schedule.py -q

closes #217

[coveralls]

Coverage Report for CI Build 28741922547

Coverage increased (+0.04%) to 96.394%

Details

• Coverage increased (+0.04%) from the base build.
• Patch coverage: 1 uncovered change across 1 file (9 of 10 lines covered, 90.0%).
• No coverage regressions found.

Uncovered Changes

File	Changed	Covered	%
src/flexmeasures_client/client.py	10	9	90.0%

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	721
Covered Lines:	695
Line Coverage:	96.39%
Coverage Strength:	2.89 hits per line

---

💛 - Coveralls

[Flix6x]

Thanks a lot for this fix, and apologies for the delay in reviewing! The base-version comparison is the right call, and the regression tests covering both the dev-0.33 asset endpoint and the older sensor endpoint fallback are much appreciated.