Fox - fix issue with export limit and v2 scheduler

[springfall2008]

No description provided.

[Copilot]

Pull request overview

This PR fixes Fox EVO (v2 scheduler) handling so that scheduler responses’ properties metadata (range/unit/precision) is preserved and used when deriving device settings (notably ExportLimit). This ensures derived settings publish as editable HA number.* entities (with min/max/step) rather than falling back to plain sensors that leave automatic_config-wired entity IDs unresolvable.

Changes:

• Preserve and forward the v2 scheduler properties block through get_scheduler_v2() into get_scheduler().
• Enhance update_settings_from_schedule() to attach range/unit/precision from properties when synthesizing settings like ExportLimit/ImportLimit/PvLimit.
• Add regression tests ensuring v2 properties are honored and derived ExportLimit publishes as a number entity; bump version to v8.44.3.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
apps/predbat/fox.py	Pass through v2 scheduler properties and use them to derive editable number settings (ExportLimit, etc.).
apps/predbat/tests/test_fox_api.py	Add regression tests for v2 properties handling and ExportLimit publishing as a number entity.
apps/predbat/predbat.py	Bump THIS_VERSION to v8.44.3.