Assistance packaging eth-hash for Debian

I am in the process of packaging eth-hash for Debian, but have run into a problem and am hoping you can assist me. The `pycryptodome` project provides an option to install its files under either the `Crypto` or the `Cryptodome` namespace.

The `Crypto` package uses the same namespace as the old `PyCrypto` library. It is installed by running `pip install pycryptodome`.

Thy `Cryptodome` package installs the same files to the `Cryptodome` namespace, making it co-installable with `PyCrypto` if desired. It is installed by running `pip install pycryptodomex`.

https://github.com/Legrandin/pycryptodome/?tab=readme-ov-file#pycryptodome

Upstream recommends using the `Cryptodome` namespace except when running in a `virtualenv`. Debian ships a binary package named `python3-pycryptodome`, which installes its files into the `Cryptodome` namespace.

https://tracker.debian.org/pkg/pycryptodome

https://packages.debian.org/sid/amd64/python3-pycryptodome/filelist

My question is, how difficult would it be to adjust `eth-hash` to be able to work with `pycryptodome` in either the `Crypto` or the `Cryptodome` namespace? If it is easy, would that be a change you would be willing to make?

If it is hard, I will go down the path of getting Debian packages for both namespaces.

Start by reading the pycryptodome documentation linked in the issue and inspecting the eth-hash package source to locate its dependency imports. Compare the Crypto and Cryptodome namespaces, then define completion as working with Debian's Cryptodome namespace while retaining compatibility with Crypto.

Written by the indexing model from the issue text.