Bump envoy/envoy_api registry pins to 1.40.0-dev.20260904.13144fb.envoy, version 0.2.7

[Copilot]

The bazel-registry re-cut envoy/envoy_api as a co-published pair at 1.40.0-dev.20260904.13144fb.envoy and deleted the previous 6609c01/16b0d47 snapshots this repo was pinned to, breaking resolution against registry HEAD.

Registry ref

• .bazelrc, filter-cc/.bazelrc, wasm-cc/.bazelrc: registry commit e71edce... → bed06c78cb1ea901164f4d248c3e5167f720e068

Module pins

• Root/filter-cc/wasm-cc MODULE.bazel: envoy/envoy_api → 1.40.0-dev.20260904.13144fb.envoy
• Module version 0.2.6 → 0.2.7 (root, filter-cc, wasm-cc), including root's sibling bazel_dep pins for envoy-example-filter-cc/envoy-example-wasm-cc, so the registry can republish all three example modules as a set at 0.2.7.envoy
• filter-cc/MODULE.bazel: fixed a pruned straggler, toolchains_llvm 1.8.0.envoy → 1.9.0.envoy (root/wasm-cc were already on 1.9.0.envoy)

CI

• .github/workflows/_verify_build.yml: updated the injected git_override commit used for build verification, 6609c01e330fb84049d54a9dbffae8609b1ec9f7 → 13144fbbb3800f1a41c45d17dc9de44978b567b1

Lockfiles

• MODULE.bazel.lock and wasm-cc/MODULE.bazel.lock: updated registry hash entries for the changed envoy/envoy_api/toolchains_llvm modules. filter-cc/MODULE.bazel.lock isn't tracked in this repo and was left alone.

Grep confirms no remaining references to 6609c01, 16b0d47, e71edce, 1.8.0.envoy, or version = "0.2.6".