Implement TechnoVE integration

[Moustachauve]

Proposed change

This adds a new integration for TechnoVE Stations. These are Electric vehicle supply equipments (EVSE).
This first PR is implementing only the sensor entity. I'll port more features, like binary sensors and services, in subsequent PRs to make the reviews manageable.

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: Add TechnoVE integration home-assistant.io#30420

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.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

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

[home-assistant]

Hi @Moustachauve

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

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

[autinerd]

Maybe splitting zeroconf into its own PR would be a good thing to keep this PR as small as possible

[joostlek]

I think I've seen zeroconf be added in the same PR. Also because zeroconf also decides what kind of unique id you pick etc. But I have no experience with zeroconf.

[Moustachauve]

Maybe splitting zeroconf into its own PR would be a good thing to keep this PR as small as possible

Done, I removed zeroconf from this PR so it can be included in a subsequent one.

[autinerd]

One question I have, is it only allowed to use IP addresses in the integration? If not, I would prefer to use CONF_HOST over CONF_IP_ADDRESS.

[Moustachauve]

One question I have, is it only allowed to use IP addresses in the integration? If not, I would prefer to use CONF_HOST over CONF_IP_ADDRESS.

The devices only have an IP address, but I guess technically one could assign a local DNS address to the device.

[autinerd]

From my view, it now looks good :)