MFA marked as undefined with a warning when it is defined and the same MFA is suggested as a solution

[probably-not]

On a fairly large project (170K lines of Elixir code), I've been experimenting with adding Expert in order to upgrade us to the latest Elixir versions.

After adding Expert and forcing a full compile and build of the project, deps, and indexes, I am receiving hundreds of the following error (MFAs are anonymized since this is in our production codebase):

MyApp.MyProtocol.function/1 is undefined (module MyApp.MyProtocol is not available or is yet to be defined). Did you mean:

      * MyApp.MyProtocol.function/1

More information to assist in debugging:

• Elixir version 1.19.5
• Erlang version 28.3
• MyApp.MyProtocol is aliased at the top of the file (alias MyApp.MyProtocol) so the code that is causing the warning is MyProtocol.function(xxx)
• When I force a save within this file, it removes the warning, however if I move to a different file and then force a save in that file, the warning comes back
• I have consolidate_protocols: Mix.env() not in [:dev, :test] set in the mix.exs.

[probably-not]

More information (replicating this from the Discord so that it's available for anyone who wants to take a crack at it):

• This issue does not happen with Expert on Elixir 1.18/OTP-27 from what I can tell on my local tests.
• I have a feeling that it may be from this merge to Elixir which went into 1.19: Load modules lazily and only if needed elixir#14453. In it, the way modules are loaded was changed to lazy loading, which caused regressions across other libraries (see this PR on Vix for example: Ensure Janitor is always autoloaded akash-akya/vix#198).
• When checking locally and adding @compile {:autoload, true} to one of the modules causing this warning, it seems to clear the warnings related to this specific module (although there are several other warnings across the entire repo due to this same problem.