`ethers` Contract Interface Fails To Load When Called With A v6 `Provider`

[dysbulic]

When attempting to call QuestChain__factory.connect using ethers v6, the call fails with the error: "invalid signer or provider" because apparently v5's Provider.isProvider() returns false when called with a v6 Provider.

The solution is likely to upgrade to ethers v6 which was, in fairness, released in February of 2023. ethers v6 is required for other libraries like the Ethereum Attestation Service. Most of the changes are just removing containing namespaces like ethers.utils.<lib> → ethers.<lib> & the same for ethers.providers.*. Also, Web3Provider becomes BrowserProvider. (I know because I just did the v6 → v5 transition to fix Quest Chains in MetaGame, breaking EAS in the process.)

[dysbulic]

I posted the following to the MetaGame Discord, and am copying it here for better visibility:

@vidvidvid or @dan13ram, in the Quest Chains sdk repository, there's a bunch of code that says it's autogenerated, but the sources don't seem to be in the sdk repository.

In poking around, I was thinking maybe the sources are in the subgraph repository. Is that so, and, if so, what is the process for regenerating the files in the sdk repository?

Also, because the switch from ethers v5 to v6 will break compatibility with v5 versions, should this code be Quest Chains v3?