Replaces the Node.js-based generate-version-header.js script with a C++
implementation to eliminate the Node.js runtime dependency from the build
process. The new C++ tool reads package.json and generates the same
version.h header file.

Also fixes Closure Compiler errors under strict mode in
extension_field_binary_info.js and map.js by properly assigning
goog.requireType calls to const variables instead of using standalone
goog.requireType calls.

Changes:
- Add generator/generate-version-header.cc with C++ implementation
- Remove generate-version-header.js
- Update generator/BUILD.bazel to use cc_binary instead of Node.js script
- Add rules_cc dependency to MODULE.bazel
- Update BUILD.bazel to remove deleted script from exports_files
- Fix goog.requireType usage in extension_field_binary_info.js and map.js

* Replace Node.js version header generator with C++ implementation

Replaces the Node.js-based generate-version-header.js script with a C++
implementation to eliminate the Node.js runtime dependency from the build
process. The new C++ tool reads package.json and generates the same
version.h header file.

Also fixes Closure Compiler errors under strict mode in
extension_field_binary_info.js and map.js by properly assigning
goog.requireType calls to const variables instead of using standalone
goog.requireType calls.

Changes:
- Add generator/generate-version-header.cc with C++ implementation
- Remove generate-version-header.js
- Update generator/BUILD.bazel to use cc_binary instead of Node.js script
- Add rules_cc dependency to MODULE.bazel
- Update BUILD.bazel to remove deleted script from exports_files
- Fix goog.requireType usage in extension_field_binary_info.js and map.js

* Add BCR boilerplate

* Add //:javascript target

* Add patch to remove dist-related bazel targets from root BUILD file

* Mark rules_pkg as a dev dependency

* bcr: remove non-google maintainer

* Remove version string in MODULE.bazel

* Add e2e/bcr to bazelignore

Also add .bazelrc configuration to disallow auto-importing previously native symbols (e.g. sh_binary)

The BCR publishing workflow requires a tag, and we can't use v4.0.1
since it didn't yet contain the actions. We will hold off doing an
actual plugin release to npm until BCR is settled.

The workflow is currently using an URL that resembles cross-compiled
protoc-gen-js zips without architecture info. Swap to using the URL
for the zips.

Release workflow currently errors out with `//:dist_files: missing
input file '//:google-protobuf.js'` because we normally only generate
it as part of the cross-compiled binary and npm releases. However,
this seems to be causing problems for the BCR release process because
the build target is broken without it.

This change just adds a placeholder file to smooth things over.

By default, the release_ruleset wants to use `bazel test //...`, but
this will fail since we have no tests registered with bazel (we use
jasmine via gulp). Instead, just try to build the tarball as a basic
check.

…271)

Switch BCR release workflow javascript source tarball, bump version

While the traditional dist tarball includes MODULE.bazel, it has an
architecture specific name that is inappropriate for BCR. The tar'd
javascript filegroup is closer to what we want, but the release
process fails when it doesn't find MODULE.bazel.

This change just splits the difference and adds MODULE.bazel to the
javascript filegroup.

* Bazel 9 cleans up a deprecated flag that is still lingering, but should be a no-op.
* Update workflows to use protobuf 33.4

Fix bug in @protocolbuffers/protoc-gen-js package that causes it to
erroneously download an older version (v4.0.0) of the plugin.