undefined packages in opam file should not reference lock dir after translation

[Alizter]

The test run-converted-opam-commands.t shows an error message that points to a lock file. However the erroneous location is really in the opam file. We should fix the location and give a better user message in this case.

Similar issues update-non-dune-local-pin.t and build failures. We shouldn't be reporting lock file locations in such build errors.

Such errors are either upstream opam repo issues or dune build failures. We need to be clear in the error message about what is wrong and how the user might fix it.

[rgrinberg]

I guess ticket assumes that we're using the auto locking mode? Otherwise I don't know where would the locations from the opam files would be discovered.

[Alizter]

Yes, these were from the autolocking PR #11775. Once that has been merged, these will need to be fixed.

[Alizter]

Closing this for the time being as I was a little too quick to open it. It's not clear if it will be an issue yet.