dump ecfs dump file format from ram with volatility

Is your feature request related to a problem? Please describe.
I am currently trying to run back in a securely protected vm a rensomware ram caught by volatility in order to find back the encryption key. Sadly the windows .dmp files do not permit to restart the process yet.

Describe the solution you'd like
As mentionned in this other repository: https://github.com/elfmaster/ecfs/blob/master/README#L47 there is already a file format for this need that does it for Linux (my ransomware is on windows). I suggest to write it for this Linux format first. Then I will do something similar for windows. Volatility should be able to extract each ecfs files from ftk imager or any imager.

Describe alternatives you've considered
-rerun a .dmp file (useless because it does not contain the informations about the variables in the state of the program).

Additional information
I have already oppened a similar feature request at this address: https://github.com/volatilityfoundation/volatility3/issues/871 During this period I did not really knew how to do it. I have a better idea now.

Here is a similar issue that describe the problem: https://superuser.com/questions/904441/possible-to-save-process-as-dump-file-to-disk-and-then-reload-the-process-later

Start by reading the ECFS format description in the referenced ecfs README and the related Volatility issue #871. Define how Volatility should extract ECFS files from an image, beginning with the Linux format. Done means the requested ECFS extraction behavior is implemented and can support the stated process-state recovery use case.