Dw/binding cacher

[dolled-possum]

Problem

Binding entries from the tokenregistry contract will need be used by other processes in the near future.

Solution

While the work has not been made in process_lib to exploit the information from the tokenregistry contract, this work runs a cacher for the data, and ensures that the scripts associated with hypermap-cacher automatically affect the binding-cacher process as well.

Testing

On super-debug verbosity, it's easy to see the impact of the start-providing, stop-providing, set-nodes, and reset-cache scripts now affecting both hypermap-cacher and binding-cacher processes. The hypermap-cache and binding-cache data are now stored in their own respective directories in vfs/hypermap-cacher:sys, and the cached records can be directly viewed there.

Notes

Because this work has incremented the version of the .wit for to add the binding-cacher interface to the hypermap-cacher world, the Cargo.toml references of the package now point to a specific commit in the process_lib repo (in the dw/hmap-binding-cacher branch, commit ac36caf)