Get MODULE.bazel from patches of archive_override/git_override

[jesses-canva]

PoC

It's common for archive_override and git_override modules to contain the entire MODULE.bazel file in their patches. In this case it's possible to provide the MODULE.bazel file for version resolution without executing the underlying repository rule.

Luckily most of the code for this already exists to apply the patches to the MODULE.bazel for a single_version_override, we just have to allow doing the same for archive_override/git_override and run the patch application without an existing file.

[Wyverald]

this shouldn't be necessary. Non-registry overrides like archive/git override already fetch the entire repo (which includes patching) before reading the MODULE.bazel file. Have you observed evidence to the contrary?

[fmeum]

Based on the description, I think that this is meant to speed up module resolution by avoiding the download of the module archive.

[Wyverald]

Ah, I missed that part. But that doesn't really make sense to me, either -- what's the baseline for the patch? You'd still need to download the whole archive first.

[fmeum]

The PR tries to detect when the patch creates the file rather than modifies one, meaning that no baseline is needed.