Some wcfs bugs are aonly likely to trigger with GOMAXPROCS=1 (see
corresponding tox.ini history), same for 2. Go-fuse also has issues with
GOMAXPROCS=1 (https://github.com/hanwen/go-fuse/issues/261) that
sometimes manifest themselves as hangs with GOMAXPROCS=`nproc` too.

- it is more clear to run wcfs tests separate
- it was confusing to run wcfs unit tests as part of e.g.
  test.py/fs1-!wcfs (note the "!wcfs" = "non-wcfs")

go.mod is inside wcfs/ and if `go test ./...` is ran outside of it, it
autodetects to use GOPATH mode and fails to find imports used by wcfs.

To run wendelin.core tests under Nexedi testing infrastructure.

* kirr/t:
  X wcfs: make it to use go modules for dependencies

Still want to preserve GOPATH compatibility as working on several
repositories simultaneously is, unfortunately, currently not good via
modules

https://github.com/golang/go/issues/27542
https://github.com/golang/go/issues/37755

For GOPATH way of work (local development) wendelin.core has to be
symlinked from inside $GOPATH/lab.nexedi.com/nexedi/ and worked through
_that_ directory - else imports inside wcfs will fail.

* master:
  3rdparty/ccan: Update for build fix wrt recent gcc/binutils

We need the following patch of mine:

   http://git.ozlabs.org/?p=ccan;a=commitdiff;h=b97c7f0841f5173a07a2571f2c99f944d8405a90

Else in case of two files used simultaneously the index is messed up.
Fixes test_wcfs_watch_2files and now all wcfs tests pass again.

Reason: see comments.
Prerequisite to fix test_wcfs_watch_2files