Bump solax to 3.2.3

[squishykid]

Breaking change

Proposed change

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: Partially reverted b2a9ac5 - missing last_reset squishykid/solax#179
• This PR is related to issue: Add support for X1 mini G4  squishykid/solax#183
• Link to dependency code change: squishykid/solax@v3.2.1...v3.2.3

Checklist

• 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.

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.

[squishykid]

Actually I will close this and raise a separate PR, i want to include another change
Cancel that, i will just update this one

[joostlek]

It would also be nice if we can finally start moving the entity definitions from the library to the integration

[squishykid]

@joostlek do you have an example or docs I can see to show what you mean by moving the entities? Let me see what I can do.

[joostlek]

You currently have all the data points and the name of the data points in the library from which you create entities. Ideally we create sensor entity descriptions in home assistant which describes what entities to expose. This allows us to translate the entity names for example