Add support for whole apsystems ez1 series

[mawoka-myblock]

Proposed change

As there are more inverters of the ez1 series by apsystems with each having another max output, this PR queries the inverter on first setup and saves the max output which is then reused for the number entity. This PR depends on #123225 and would resolve #122979

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:
• Link to documentation pull request: Explain Apsystems entities in tables rather than lists home-assistant.io#34200

Checklist

• The code change is tested and works locally. (TODO)
• Local tests pass. Your PR cannot be merged unless tests pass (TODO)
• 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. (TODO)

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 link to the changelog, or at minimum a diff between library versions 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.

[home-assistant]

Hey there @SonnenladenGmbH, mind taking a look at this pull request as it has been labeled with an integration (apsystems) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of apsystems can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign apsystems Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[joostlek]

We do have a coordinator right? You can move this to _async_setup a new lifecycle function for the coordinator

[mawoka-myblock]

Okay, so I've now moved it into the coordinator

[joostlek]

Why do we store this in self.api? Shouldn't we store this at the coordinator

[mawoka-myblock]

Because the api needs this as well, as it checks against that as well and why storing it in the api and the coordinator when the api needs it regardless of the coordinator?

[joostlek]

It sounds strange that the API requires it tbh, why do we receive the value to set it afterwards, why don't we call a function for the api to just set it themselves.

Also, can this raise? We should raise UpdateFailed in that case

[mawoka-myblock]

The reason is that the API shouldn't run any IO in the init function so that it can be initialized when the inverter is offline

[mawoka-myblock]

Thanks!