bazel-based continuous integration flow

[matthew-levan]

This PR implements CI workflows for:

• Binary builds (all four supported platforms: macos/linux, x86/arm)
• Tests (i.e., c3, ent, noun, ur, and vere tests)
• Releases (binary uploads to GCP) for pre-release and release tags
• Docker builds
• Ship tests
• Caching

Workflows from urbit/urbit have been refactored for improved clarity, and nix derivations previously used in CI have been extracted and implemented with bazel.

Resolves #8.
Resolves #9.
Resolves #25 via #28.
Resolves #26 via #34.
Resolves #29.
Resolves #30.
Resolves #32 via #33.
Resolves #35 via #37.

[mcevoypeter]

This is only a partial review. I haven't looked through the CI scripts or the Docker markdown doc yet.

[mcevoypeter]

LGTM

[matthew-levan]

When branching this runtime-specific repo off from the urbit monorepo, we initially based off of next/vere in the monorepo. However, during the course of fall 2022, buggy work ended up on next/vere. Because of this, the release branch for version 1.14 of the runtime branched off of master, not next/vere, leading to a non-trivial divergence between next/vere and master. To that end, we have to rewrite the history of this repo, which will potentially obfuscate the commit SHAs and diffs of the already merged PRs in this repo. To provide a trail of breadcrumbs, attached is a patch of the diff represented by this PR before history was rewritten.

PR21.patch