table: use golang version zstd to replace the old one to make badger and unistore portable

[jackysp]

Signed-off-by: Shuaipeng Yu jackysp@gmail.com
PTAL @coocood

[coocood]

Have you run go test?

[bobotu]

In addition to ZSTD, the following issues prevent us from allowing running unit tests on Windows:

1. The os.OpenFile miss a flag on Windows platform, make the behavior of delete an opened file different with POSIX environment. (See proposal: os: Create/Open/OpenFile() set FILE_SHARE_DELETE on windows golang/go#32088)
2. ResourceManager and blobGCHandler doesn't close and free resources after DB.Close, so some test case will meet The process cannot access the file because it is being used by another process, The requested operation cannot be performed on a file with a user-mapped section open when reopen DB
3. DirectWriter.Finish try to truncate the file to actual size, but Windows doesn't allow doing this on an O_DIRECT file, the returned error is truncate: The parameter is incorrect. Fortunately, this is easy to fix, we can open this file in normal mode and do truncate. (See https://docs.microsoft.com/zh-cn/windows/win32/fileio/file-buffering#alignment-and-file-access-requirements)
4. We should use path/filepath instead of path to work on file's path.
5. Seems there are some memory-leak in some test case. I have got OOM on my laptop.

[bobotu]

BTW, it seems like some workers will terminate when a filesystem error occurred, but these workers will never start again and the database becomes unavailable.