Fix up lit's tests to run in a multi-config environment

[jdenny]

What do you think of placing that empty lit.cfg directly within Inputs instead? I think this would generally isolate all Inputs/* test suites from lit/tests/lit.site.cfg and thus avoid such confusion for future tests.

Of course, we might not create any new tests for nonexistent directories, but we might do something else. For example, if we were to forget to create a lit.cfg in some new Inputs subdirectory and it inadvertently came to depend on some configuration item from lit/tests/lit.site.cfg as a result, the new tests might pass locally but then fail under Windows in the manner we just saw. However, if it couldn't pick up lit/tests/lit.site.cfg, then hopefully we'd notice the missing configuration item on any platform.

[probinson]

Move the empty lit.cfg to Inputs; undo selecting.py change.

[probinson]

Done. Makes sense to avoid future mishaps.

[jdenny]

LGTM. Thanks!

[yln]

Thank you Joel and Paul!

llvm/utils/lit/tests/Inputs/lit.cfg

+# A deliberately empty lit.cfg, so that test discovery under the Inputs
+# directory doesn't inadvertently try to load lit/tests/lit.site.cfg (which
+# will fail in a multi-config environment such as Visual Studio or Xcode).