fs: fix glob case-sensitivity inconsistencies

[louiellan]

Refs: #58991

fix matchers' nocaseMagicOnly option where it makes any non-magical/literal pattern case-sensitive which results to:

1. making the exclude option case sensitive which shouldn't be on Windows and macOS,
2. any casing difference in matched list not to be filtered out
3. not returning the true casing of a matched directory / file

Could be notable-change because i suspect since this bug has been out for a while, i expect that developers might had some sense that the exclude option has always been a case sensitive part of the fs.glob, regardless of the operating systems quirks on case-sensitivity file system

[louiellan]

For additional info

with a directory structure:

a
   |---> index.txt
sample.js

sample.js

const fs = require('node:fs')

// test-1
let files = fs.globSync('a/index.TXT', { exclude: ['a/index.txt'] })
console.log(files)

// test-2
files = fs.globSync('a/index.TXT', { exclude: ['a/in*dex.txt'] })
console.log(files)

// test-3
files = fs.globSync('a/index.TXT', { exclude: ['a*/index.txt'] })
console.log(files)

In test-2, with merely the presence of a glob character in pattern, the file gets excluded (case-insensitively)
with only a literal string, like those in test-1 and test-3 where the filename itself does not have a glob character, the file doesn't get excluded

the test-1 and test-3 should filter the file just like the test-2 as they're technically the same