Cabal <<loop>>s upon encountering a invalid new-run target.

[AndreasPK]

Repro case:

git clone https://github.com/ndmitchell/safe.git

And run new-run with an invalid target.

Andi@Horzube MINGW64 /c/temp/safe
$ cabal new-run exe:algorithms
cabal.exe: Internal error in target matching. It should always be possible to
find a syntax that's sufficiently qualified to give an unambiguous match.
However when matching 'exe:algorithms' we found exe:algorithms
(unknown-component) which does not have an unambiguous syntax. The possible
syntax and the targets they match are as follows:
cabal.exe: <<loop>>

Original example

cabal --store-dir=/home/Andi/.store_all new-run --builddir=d-all -w 'C:\ghc\msys64\home\Andi\trees5\allCalls\inplace\bin\ghc-stage2.exe' '--ghc-options=-fnew-blocklayout -fcfg-weights=callWeight=310' --enable-benchmarks --disable-tests exe:algorithms -- --csv ../benchResults/allCalls.all.algorithms.csv
cabal.exe: Internal error in target matching. It should always be possible to
find a syntax that's sufficiently qualified to give an unambiguous match.
However when matching 'exe:algorithms' we found exe:algorithms
(unknown-component) which does not have an unambiguous syntax. The possible
syntax and the targets they match are as follows:
cabal.exe: <<loop>>

[typedrat]

Doesn't loop on macOS.

Doesn't work, either:

~/Development/safe master
❯ cabal new-run exe:algorithms
cabal: Internal error in target matching. It should always be possible to find
a syntax that's sufficiently qualified to give an unambiguous match. However
when matching 'exe:algorithms' we found exe:algorithms (unknown-component)
which does not have an unambiguous syntax. The possible syntax and the targets
they match are as follows:
'exe:algorithms' which matches exe:algorithms (unknown-component),
:pkg:exe:lib:exe:file:algorithms (unknown-file)

[grayjay]

I think this is a duplicate of #5081. #5263 fixed the infinite loop, but there is still an internal error.

[grayjay]

Duplicate of #5081