Switch to official Zabbix Python API

[kruton]

Breaking change

This change drops support for Zabbix 4 and before. Only Zabbix 5+ versions are supported.

Proposed change

Currently the Zabbix component is broken with Zabbix 5.4 or newer, because the API changed to require "username" instead of "user" to login at that point.

The Zabbix project released an official Python API library called "zabbix_utils" which can replace the current library that this component is using.

This just does a conversion to the existing synchronous API. The new Python library also supports an asynchronous API which could be used to further migrate this plugin.

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 Zabbix Integration: API Logon fails, Integration uses wrong Parameter for username? #90341 and fixes Zabbix Integration dont work #103786
• This PR is related to issue: N/A
• Link to documentation pull request: None necessary

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.

[home-assistant]

Hi @kruton

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.

Stale

[dotvav]

Starightforward 1-to-1 migration. LGTM 👍

[edenhaus]

Sanity check of zabbix-utils==2.0.1 ✔️

Does the current integration support Zabbix < 5? If yes, we need to add a breaking change section to this PR

[kruton]

Sanity check of zabbix-utils==2.0.1 ✔️

Does the current integration support Zabbix < 5? If yes, we need to add a breaking change section to this PR

Good call. According to an archived copy of their release policy, Zabbix 4.x stopped receiving full support in Oct. 2021 and limited support in Oct. 2023. I imagine that means the impact for this breaking change will be almost zero.

Is there any special format needed to indicate a breaking change in the description that gets rolled into release notes?

[edenhaus]

Please fix the CI

[edenhaus]

Is there any special format needed to indicate a breaking change in the description that gets rolled into release notes?

Tagging it with breaking-change

[kruton]

Please fix the CI

Done.

[kruton]

Looks like there was an existing mypy error on another module. Merged in latest 'dev' to hopefully avoid that.