v1.10.6-alpha.2

Second experimental alpha for issue #49 based on tester feedback from v1.10.6-alpha.1.

Changes:

• Experimental Base Load Power no longer uses powGetSysLoad as its state. Tester logs confirmed that field tracks live output/load, not the configured base-load setpoint.
• The entity now reads the configured schedule from dayResidentLoadList.load[].loadPower.
• The write candidate now sends cfgDayResidentLoadList while preserving the existing schedule windows and replacing each existing period's loadPower.

Important notes:

• This is still a validation alpha. EcoFlow's public docs still do not document this write payload.
• A single Home Assistant number cannot fully model multiple schedule periods with different values. If multiple schedule periods have different loadPower values, the entity reports the currently active period when possible.
• Setting the number updates all existing schedule periods to the same load power.
• If dayResidentLoadList.load is empty, create a schedule period in the EcoFlow app first, then test again.

Verification:

• python -m unittest tests.test_stream_base_load_mapping
• python -m compileall custom_components\ecoflow_api tests
• python -m json.tool custom_components\ecoflow_api\manifest.json
• git diff --check