Compiler checks wrong output path when project folder name ends in .odin

[refual]

Context

• Operating System & Odin Version:

Odin:    dev-2024-04-nightly:aab122ede
OS:      Ubuntu 22.04.3 LTS, Linux 6.5.0-21-generic
CPU:     Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz
RAM:     15867 MiB
Backend: LLVM 17.0.6

Expected Behavior

When running odin build ., I expect the resulting executable to be created inside the current project folder without the compiler unnecessarily concerning itself with the parent folder.

Current Behavior

When the project folders name contains a dot and the parent folder contains a directory with the same basename (i.e. without the extension) as the resulting executable, the compiler will complain about the name conflict.

Steps to Reproduce

Please provide detailed steps for reproducing the issue.

mkdir -p Projects/test{,.odiin}
cd Projects/test.odiin
touch main.odin
odin build .

The compiler thinks the Projects/test folder collides with the output file even if (once that folder is moved away) the resulting executable is placed in Projects/test.odiin/test.odiin as expected, i.e. different folder and file names. This still works if Projects/test is not actually a directory at all.

A different output path specified using -out (as suggested by the error message) is completely ignored by this check, too.

As an added bonus the versions later than 2024-03 do not even print any errors and just fail silently:

$ ~/.local/opt/odin-dev-2024-03/odin build . ; echo $?
Please specify the executable name with -out:<string> as a directory exists with the same name in the current working directory1
$ ~/.local/opt/odin-dev-2024-04/odin build . ; echo $?
1

[Kelimion]

Fixed in #3958.