Add battery charge current limit number entity to GoodWe - #180296

Proposed change

Adds a Battery charge current limit number entity to the GoodWe integration, exposing the inverter's battery_charge_current setting (Modbus register 45353) under the device's configuration entities.

The entity is only created when the inverter advertises the setting (inverter.settings() contains battery_charge_current), so model families without the register get no entity and no register read is attempted. It is read/written through read_setting/write_setting with the register's 0.1 A resolution (a converter field was added to the entity description so the existing whole-number settings keep their int conversion while this one uses round(value, 1)).

The 0–100 A range is GoodWe's documented range for the register (BattChargeCurrMax RW U16 gain 10 [0,1000] in the ARM Modbus protocol map), not a per-model hardware limit; per that documentation the inverter and battery BMS still apply their own real-time limits. It's a current ceiling: actual charging power depends on battery voltage, available PV power, load, inverter mode and BMS limits. The entity uses box input mode (no slider) and EntityCategory.CONFIG.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue: Goodwe Make battery_charge_current changeable mletenay/home-assistant-goodwe-inverter#413 (also Add custom entries to logbook #363 and Nest temperature Range Values #287)
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies a diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.