[core] Move to bzlmod for handling dependencies

[dayshah]

Description

Currently Ray uses the outdated WORKSPACE / http_archive way to get dependencies and build them. For example, see https://github.com/ray-project/ray/blob/master/bazel/ray_deps_setup.bzl used in https://github.com/ray-project/ray/blob/master/WORKSPACE. We shouldn't define dependency builds like this, ex. for nlohmann_json we have https://github.com/ray-project/ray/blob/master/bazel/nlohmann_json.BUILD and

ray/bazel/ray_deps_setup.bzl

Lines 345 to 351 in f0a408a

	http_archive(
	name = "nlohmann_json",
	strip_prefix = "json-3.9.1",
	urls = ["https://github.com/nlohmann/json/archive/v3.9.1.tar.gz"],
	sha256 = "4cf0df69731494668bdd6460ed8cb269b68de9c19ad8c27abc24cd72605b2d5b",
	build_file = "@com_github_ray_project_ray//bazel:nlohmann_json.BUILD",
	)

.

Instead we should use migrate to bzlmod and use the bazel central registry as almost all of our dependencies can be found there. Ex. https://registry.bazel.build/modules/nlohmann_json. This will make dependency builds more consistent and make upgrades way less painful.

This is the guide to do the migration to bzlmod https://bazel.build/external/migration, ideally we should go with the gradual migration route and do each dependency one by one.

Use case

No response