Argument globbing (expansion) on Windows causes arguments intended as patterns to be prematurely expanded

In ls for example, the --ignore flag expects a pattern.

In windows, these flags are prematurely expanded, so patterns become actual files, which are then ignored when they should not be.

For example, in test_ls_ignore_explicit_period, two files are created:

• .hidden.yml
• regular.yml

When this command is executed: ls -a --ignore ?hidden.yml, the desired outcome is that both .hidden.yml and regular.yml are listed, because filename matching in ls requires explicit .s for hidden files.

On windows, the ?hidden.yml is expanded by wild::args() to .hidden.yml. When matching, the new argument .hidden.yml is a perfect match, and has a leading ., which causes it to be hidden (not the expected output)

More details here: https://github.com/uutils/coreutils/pull/3803

The premature globbing causes problems in some cases. We should investigate how the globbing can be refactored.

Start with the test_ls_ignore_explicit_period case and trace how Windows arguments reach wild::args(). Determine how the --ignore pattern should remain unexpanded, then verify that the test lists both .hidden.yml and regular.yml on Windows without regressing other argument globbing behavior.