Set up for Bazel module builds.

[bcsgh]

Notes:

1. This likely doesn't require a release note as it shouldn't have any effect on any released product.
2. The MODULE.bazel is forked from the "bazel-central-registry" and this allows the BCR to quit having to uses patches.
3. With these changes JsonCpp can be built by Bazel without any changes. Without this, Bazel is unable to locate a correct root to build from and fails.
4. This effectively supersede Define jsoncpp as Bazel module #1534 ;; Addressing comments from there:
   1. The version in MODULE.bazel should track the version used everywhere else. This just becomes yet-another-copy of that.
   2. WORKSPACE is dead (though one would be needed ... if someone had to JsonCpp, as a root module, with Bazel, and without using modules, which should be nobody ever again).
   3. I'm not including a .bazelrc as things should "just work" (unless your ~/.bazelrc does something annoying).

---

It would be nice if making updates to BCR became part of the normal release process. It looks like that could be rather easy with the available tool support maybe even automated.