Deoldify Vapoursynth filter

[Dan64]

Hello Selur,

  good news! I solved the problem regarding the GPU memory usage of ColorMNet when run inside Vapoursynth environment.
  I wrote a frame server that run in a separate thread and different environment. In this way the GPU usage is very low (<2GB even with 20000 frames).

  This is an innovative approach that allow to run inside Vapoursynth render programs that are too complex to be executed in the Vapoursynth environment.

   I tried to reduce the changes, so that I added only a new parameter: server_port which represent the network port used to exchange data between Vapoursynth and the remote frame server.

   I decided to keep, for the moment, the 3 encoding modes of ColorMNet, the only difference is that the mode:0 (named "batch") has been renamed in "remote" and represent the new encoding mode that uses the remote frame server. This mode is now the default encoding mode for ColorMNet.
  I tested it, and it seems to be quite robust, in any case I decided to keep the mode:1 (async) e 2 (sync) in the case there are problems in using the "remote" mode.

  Given that the new "remote" mode will allow to monitor the progress, there is no reason to implement a progress monitor for the "sync" mode, which probably will be removed when the "remote" mode will be fully tested with different environments and PCs and will be considered robust.

  I think that this is the first filter for Vapoursynth developed in this way and I prefer to take time to test it.

  Please try it and let me know what you think.

Thanks,
Dan

P.S.
Attached the new RC17 with the new "remote" rendering