Bazel: Support local_path_override

[nnobelis]

The user can specify that a dependency should come from a certain directory on local disk.
See https://bazel.build/rules/lib/globals/module#local_path_override.

Example in MODULE.bazel:

local_path_override(
    module_name = "locator",
    path = "./tools/bazelbuild/modules/locator",
)

ORT should support this alternate locations for downloading the source code.

@haikoschol FYI

[nnobelis]

Supporting this feature seems to be a bit tricky.

Bazel does provide some of the override information in the build file:

"localOverrideHashes": {
   "test_module": "0444b4db8c556a0c4e2fbf7407f3f9c1b9a1733dc872776daa8df2678470d146",
   "bazel_tools": "922ea6752dc9105de5af957f7a99a6933c0a6a712d23df6aad16a9c399f7e787"
 },

BUT:

• This information has been removed from the lock file starting from the version 7.2.0: https://bazel.build/versions/7.2.0/external/lockfile (compare the versions using the selector top right)
• Even if we implement fetching the override information using the lock file, this would provide us only the module_name part above and we would still be lacking the path part.

I asked the Bazel's Slack channel if there were alternative to parsing the MODULE.bazel file ourselves.
They suggested using the buildozer tool instead (https://github.com/bazelbuild/buildtools/blob/main/buildozer/README.md#buildozer) with a command such as:
buildozer 'print module_name path' //MODULE.bazel:%local_path_override

It sorts of work but there is a bug with it:
bazelbuild/buildtools#1286

They recommended a workaround but I find it a bit hackish. Any opinion ?