silkworm: disable in release binaries

[battlmonstr]

A short-term safety measure to keep release.yml GH workflow unaffected.

[yperbasis]

Why do this? Hopefully we can sort Silkworm issues out before we cut next release from devel.

[battlmonstr]

@yperbasis There are a few things to be done to make it work properly: libsilkworm needs to be copied to the corresponding produced tar.gz files, test it in the release.yml workflow, and test that the resulting binaries work, also copy into docker images and test. I have it on my task list, but I wasn't sure I can sort this out in time before the next release. When is the next release devel cut-off planned?

[yperbasis]

@yperbasis There are a few things to be done to make it work properly: libsilkworm needs to be copied to the corresponding produced tar.gz files, test it in the release.yml workflow, and test that the resulting binaries work, also copy into docker images and test. I have it on my task list, but I wasn't sure I can sort this out in time before the next release. When is the next release devel cut-off planned?

Right, I see. Not sure when the next release happens. Let's go with this change to be on the safe side.