`glob_with` case insensitivity seems broken

In developing globtest (crate here), I seem to have run into an issue where the case_sensitive paremeter of MatchOptions is completely ignored in the match_with function.

Here's an example:

mqudsi@ZBook /m/c/U/M/g/globtest> globtest -d "*"

        options {
                case_sensitive: true,
                require_literal_leading_dot: true,
                require_literal_separator: true
        };

Cargo.lock
Cargo.toml
LICENSE
README.md
src
target

mqudsi@ZBook /m/c/U/M/g/globtest> globtest -d "target"

        options {
                case_sensitive: true,
                require_literal_leading_dot: true,
                require_literal_separator: true
        };

target

mqudsi@ZBook /m/c/U/M/g/globtest> globtest -id "Target"

        options {
                case_sensitive: false,
                require_literal_leading_dot: true,
                require_literal_separator: true
        };

Start with MatchOptions and the match_with function, then reproduce the report using the globtest commands and the target/Target examples. Trace how case_sensitive is handled and add coverage for both true and false settings; done means case-sensitive matching distinguishes the names while case-insensitive matching finds target for Target.