Mislabeling of eTLD-`n`

As mentioned in https://github.com/publicsuffix/list/pull/1872#issuecomment-1863614188

Multiple `psl` libraries share the same bug while handling wildcards.

> I went over all the FOSS implementations in https://publicsuffix.org/learn/ , and I found 3 of them behave funny for `wildcard` domains. In particular:
>
> * [regdom-libs](https://github.com/usrflo/registered-domain-libs/)
> * [publicsuffix2](https://pypi.python.org/pypi/publicsuffix2/)
> * [publicsuffixlist.js](https://github.com/gorhill/publicsuffixlist.js)
>
> Seems to all mislabel eTLD-`n` `x` [eTLD minus `n`] (with n from `0` to `infinite`), as an eTLD, if another eTLD `y` is defined as a subdomain of that `x` eTLD-`n`.
>
> As an example `publicsuffix2` behaviour with the following patch:
>
> ```
> // Linode : https://linode.com
> // Submitted by
> members.linode.com
> -nodebalancer.linode.com
> +*.nodebalancer.linode.com
> +*.linodeobjects.com
> +ip.linodeusercontent.com
> ```

Example here:


This bug has already been reported in this library [here](https://github.com/nexB/python-publicsuffix2/issues/21)