Use glob_match instead of globset

[zifeo]

https://github.com/devongovett/glob-match

[abdiu34567]

Hello! 👋

I'm interested in working on this issue to replace globset with glob-match. I've taken a preliminary look at the codebase, and I believe I can tackle this. Before I dive in, I'd like to clarify a few points:

Reason for Switch: Can you provide a bit more context about why we're considering this switch? Are there any specific advantages of glob-match over globset that I should be aware of?

Backward Compatibility: Do we aim to ensure complete backward compatibility in behavior, or are slight deviations acceptable as long as the primary functionality remains consistent?

Existing Tests: Are there existing tests that cover the functionalities using globset? If yes, I'll ensure they all pass after the switch. If not, I'll aim to write tests to ensure the behavior is consistent.

Deprecation: Post the switch, do we intend to deprecate all globset functionalities immediately or will there be a transition phase?

Looking forward to your insights. Once I have a clearer picture, I'll start with the implementation.

[zifeo]

@abdiu34567 Thanks for asking for some details:

• Reason for Switch: glob-match provides more advanced syntax, and globset is primarily used for ripgred, it might not fit other use cases. Also see the benchmark in the repo, it is significantly faster.
• Backward Compatibility: deviation acceptable if their improve the user experience.
• Existing Tests: none I believe. However if you find a way to test this without increasing too much the surface maintenance, welcome to add some.
• Deprecation: hard switch, no need to keep previous version working.