capnp-cpp@1.4.0

[pgerell]

Adds Cap'n Proto C++ v1.4.0 to the registry.

Patches:

• update-module-version.patch: Updates the version field in MODULE.bazel from 1.1.0 to 1.4.0 (the upstream source was not updated when the release was cut).
• bazelmod-compatible-boringssl.patch: Replaces @ssl with @boringssl//:ssl in kj-tls for Bzlmod compatibility.
• fix-ez-rpc-includes.patch: Fixes bare includes in ez-rpc.h that don't work with Bazel's sandboxed include paths (see Build error + fix when using capnp/ez-rpc with bazel capnproto/capnproto#1942).

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[bazel-io]

Hello @sebastianbergt, modules you maintain (capnp-cpp) have been updated in this PR.
Please review the changes. You can view a diff against the previous version in the "Generate module diff" check.

[pgerell]

@bazel-io skip_check unstable_url

[sebastianbergt]

LGTM, thank you @pgerell !

[bazel-io]

All modules in this PR have been approved by their maintainers. This PR will be merged if all presubmit checks pass.

[pgerell]

@bazelbuild/bcr-maintainers Is there anything I need to do?

[pgerell]

Hi @meteorcloudy, are you the right person to ask about unblocking the Buildkite presubmit?

[jwnimmer-tri]

FYI now that #8460 has landed, I think if you push any new update (e.g., rebase to latest main and force-push) the bcr_validation will pass -- it looks like all of the changes are probably innocuous.