### Summary

This was likely caused by the refactoring in abacf6a108b038571a0c3daeae63da0897c8fcb6; the old code was calling `list_deprecations()` from `AnsibleModule._handle_no_log_values()`, and the new code renamed the function to `_list_deprecations()`, but doesn't seem to call it *at all*. (There also seem to be no integration tests for this, so this went unnoticed.)

Ref: https://github.com/ansible-collections/community.zabbix/issues/857#issuecomment-1354637050

### Issue Type

Bug Report

### Component Name

AnsibleModule / argument spec validation

### Ansible Version

```console
2.11 to devel
```


### Configuration

```console
-
```


### OS / Environment

-

### Steps to Reproduce

-

### Expected Results

-

### Actual Results

```console
-
```


### Code of Conduct

- [X] I agree to follow the Ansible Code of Conduct
"""Validated and coerced parameters."""
        return self._validated_parameters
    @property
    def unsupported_parameters(self):
        """:class:`set` of unsupported parameter names."""
        return self._unsupported_parameters
    @property
    def error_messages(self):
        """:class:`list` of all error messages from each exception in :attr:`errors`."""
        return self.errors.messages
class ArgumentSpecValidator:
    """Argument spec validation class
    Creates a validator based on the ``argument_spec`` that can be used to
    validate a number of parameters using the :meth:`validate` method.
    """
    def __init__(self, argument_spec,
                 mutually_exclusive=None,
                 required_together=None,
                 required_one_of=None,
                 required_if=None,
                 required_by=None,
                 ):
        """
        :arg argument_spec: Specification of valid parameters and their type. May
            include nested argument specs.