Upgrade to Bazel 8.0.0

[KateBlueSky]

Description

Changes to upgrade to Bazel 8.0.0

• Created a MODULE.bazel file with the dependencies in it.
• Removed the WORKSPACE file
• Changed the compiler registration to be in the MODULE.bazle file (https://bazel.build/external/migration#register-toolchains)
• Added the --noincompatible_disallow_empty_glob to the bazelrc for change in native.glob behavior in bazel 8.0.0 vs bazel 7.0.0 (https://bazel.build/reference/command-line-reference)
• Updated the Ubuntu version to ubuntu-24.04, this was to be able to pull in the latest ar utility for linking static libraries. In ubuntu-22.04 had an isssue linking the static libraries using the bazel 8.0 directory names.
• Added -Wno-dangling-reference to gcc compilation for a false positive possibly dangling reference error in //examples/oneapi/cpp:subgraph_isomorphism_batch_host bazzel test.

All of these changes can be found in the bazel migration guide (https://bazel.build/external/migration)

---

PR should start as a draft, then move to ready for review state after CI is passed and all applicable checkboxes are closed.
This approach ensures that reviewers don't spend extra time asking for regular requirements.

You can remove a checkbox as not applicable only if it doesn't relate to this PR in any way.
For example, PR with docs update doesn't require checkboxes for performance while PR with any change in actual code should have checkboxes and justify how this code change is expected to affect performance (or justification should be self-evident).

Checklist to comply with before moving PR from draft:

PR completeness and readability

• I have reviewed my changes thoroughly before submitting this pull request.
• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation to reflect the changes or created a separate PR with update and provided its number in the description, if necessary.
• Git commit message contains an appropriate signed-off-by string (see CONTRIBUTING.md for details).
• I have added a respective label(s) to PR if I have a permission for that.
• I have resolved any merge conflicts that might occur with the base branch.

Testing

• I have run it locally and tested the changes extensively.
• All CI jobs are green or I have provided justification why they aren't.
• I have extended testing suite if new functionality was introduced in this PR.

Performance

• I have measured performance for affected algorithms using scikit-learn_bench and provided at least summary table with measured data, if performance change is expected.
• I have provided justification why performance has changed or why changes are not expected.
• I have provided justification why quality metrics have changed or why changes are not expected.
• I have extended benchmarking suite and provided corresponding scikit-learn_bench PR if new measurable functionality was introduced in this PR.

[ethanglaser]

/intelci: run

[ethanglaser]

The docs on this aren't super clear to me - what would happen if this flag is not added?

[KateBlueSky]

In Bazel 8.0, the flag --incompatible_disallow_empty_glob will default to true. This means that the allow_empty argument defaults to False on all glob calls. In Bazel 7.0 --incompatible_disallow_empty_glob defaulted to False and the allow_empty argument defaults to True on all glob calls. Some of the glob calls in the project return empty list, so in bazel 8.0 those glob calls that return empty list error out without setting allow_empty set to true.

[ethanglaser]

/intelci: run

[Alexandr-Solovev]

/intelci: run

[KateBlueSky]

/intelci: run

[KateBlueSky]

/intelci: run

[david-cortes-intel]

Thanks, I think this should solve the dangling reference issue, but would nevertheless be ideal to have a valgrind run executing this jaccard/vertex algorithm code just to make sure.