Misleading error: "Could not find target contract"

[MegaRedHand]

Describe the bug

When running deployment scripts with a single contract named differently than the file, deployment fails and the task logs end with "Could not find target contract".

To Reproduce

Running this local hello-world example results in that error because of Layr-Labs/hello-world-avs#97. This doesn't happen with the remote example because forge script automatically fills the contract name with the only contract inside the files. Since we flatten local scripts, however, this doesn't work for the local example.

Expected behavior

The contract name is auto-filled same as when running forge script locally.