fix outdated volatility3 dependency

[YannMagnin]

As quickly discussed with @Ston14 , this is a small trick in the pyproject.toml to force fetch the latest version of the Volatility3 using the original code base instead of the outdated package from PiPy.

Also note that Volatility3 installs the minimum dependencies as possible as a default (in its pyproject.toml) and uses a dynamic feature from setuptools to allow users to request the full installation of the framework.....feature witch poetry does not have.

So, as a workaround, I have simply dumped in our pyproject.toml all "optional" dependencies from the Volatility3 requirements.txt file]. This implies to always check in the future that this file has not been changed.

Maybe using git submodule could help us avoid this maintaining task ?