ICU-23223 Update Bazel configuration and dependencies for ICU (Bazel 7.6.1, bzlmod support)

[mmorel-35]

Description

• Bump Bazel version to 7.6.1 in .bazeliskrc
• Add common flag for Bazel module support in .bazelrc
• Include MODULE.bazel file for module definition
• Add WORKSPACE.bzlmod file for module workspace
• Update BUILD file to include necessary headers
• Add MODULE.bazel.lock to .gitignore

[mmorel-35]

I created an account on jira but couldn't create an issue, can someone help on that ?

[jira-pull-request-webhook[bot]]

Notice: the branch changed across the force-push!

• MODULE.bazel is different

View Diff Across Force-Push

~ Your Friendly Jira-GitHub PR Checker Bot

[echeran]

Although the PR description matches what the PR is doing, it's still not clear why the PR was created. In other words, what is the desired end goal that this PR solves (partially or wholly)?

Note: ICU only uses the Bazel build for building Unicode data that gets included in the headers of C++ files. Doing so requires building tools that depend circularly on those data header files.

[mmorel-35]

Starting with Bazel 9, bzlmod is the only officially supported dependency management mode. This means that new Bazel releases will exclusively support MODULE.bazel for external dependencies, and WORKSPACE-based dependency management is deprecated.

ICU is widely used in projects that build with Bazel including Envoy, Envoy Mobile, and many others in the cloud-native and open-source ecosystems. These projects are actively migrating to bzlmod to ensure compatibility with future Bazel releases and to leverage improved dependency resolution, reproducibility, and ecosystem integration. See https://github.com/envoyproxy/envoy/pull/40692

Supporting bzlmod in ICU will ensure that downstream users can seamlessly integrate ICU with modern Bazel workflows and avoid compatibility issues as Bazel evolves.

Please let me know if you need more information or specific migration guidance!

[jira-pull-request-webhook[bot]]

Hooray! The files in the branch are the same across the force-push. 😃

~ Your Friendly Jira-GitHub PR Checker Bot

[jira-pull-request-webhook[bot]]

Hooray! The files in the branch are the same across the force-push. 😃

~ Your Friendly Jira-GitHub PR Checker Bot

[mmorel-35]

@markusicu ,

Whenever you can find the time to review ;)