path: add exclude option to matchesGlob method

[mag123c]

This PR enhances the path.matchesGlob() method by adding comprehensive exclude pattern support to provide feature parity with fs.glob() and improve developer experience when filtering paths.

In the current implementation, path.matchesGlob() lacks advanced filtering capabilities, making it difficult for developers to exclude specific paths or directory trees without writing complex, error-prone manual exclusion logic. This limitation creates inconsistency between path matching utilities and forces code duplication across projects.

The updated implementation now includes:

• Enhanced API with exclude option supporting flexible exclusion patterns through strings, arrays, or custom functions that can filter out matching paths and their descendants
• Comprehensive exclude pattern types covering simple string exclusions, multiple pattern arrays for complex filtering scenarios, and function-based exclusion logic for advanced use cases
• Consistent behavior with fs.glob() ensuring unified glob matching experience across file system operations and virtual path filtering
• Improved developer ergonomics eliminating the need for manual exclusion logic and reducing code complexity when working with path pattern matching
• Robust test coverage demonstrating exclude functionality across various pattern combinations, edge cases, and integration scenarios

This change resolves#59015 by providing the requested exclude functionality that allows developers to efficiently filter paths without manually implementing complex exclusion patterns, bringing path.matchesGlob() to feature parity with other Node.js glob utilities.

[github-actions]

This pull request has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.

[mag123c]

Is an exclude option on path.matchesGlob() something the project actually wants? Right now #58988 documents the API as explicitly not having one, and @mizulu asked for the same capability over there, so the demand seems real but the direction was never settled here.

Happy to rewrite this on top of the current matcher cache if a collaborator thinks it is worth having, and equally happy to close it if in-memory path matching should stay minimal and fs.glob() remains the place for filtering.