Here is the Zuul log when you tried to publish 2.2.0 on October 6th: https://57ca86571183662f5510-aab07e4ca2931373d50feaec98dcbf9c.ssl.cf5.rackcdn.com/870b4e8c919b637f48ff836f5660ee5df0e95406/release/release-ansible-collection-galaxy/811f679/job-output.txt
The relevant part is:
2023-10-06 18:38:19.525376 | controller | ERROR! Error when publishing collection to release_galaxy (https://galaxy.ansible.com/api/) (HTTP Code: 403, Message: You do not have permission to perform this action. Code: permission_denied)
The cause is that the account that Zuul uses to publish collections lost access to all (or a least most) of its namespaces: Bot used for publishing has lost namespace access That was fixed roughly when you tried to publish your collection, so maybe you were a bit too early.
You should try to delete the tag on GitHub and re-push it. That tells Zuul to try to publish it (again). This usually works (assuming the problem isn’t with the collection itself, which doesn’t look to be the case here).
In any case, you should delete the v2.2.0 tag, since that is definitely broken (Update galaxy.yml (#1103) · ansible-collections/community.zabbix@b93862d · GitHub - the version number is invalid as it starts with v).