Make include-verification case insensitivity configurable on windows

### Description of the feature request:

We build on windows first and linux second. Windows is used by developers. Linux is a secondary platform. It would be extremely helpful if we could receive the same error messages regarding mismatched case of include paths vs filenames on windows as we will do on linux.

The behaviour has recently been fixed (in the wrong direction for us): https://github.com/bazelbuild/bazel/pull/28810

e.g `common --windows_include_verification_case_insensitivity=True` (default)

Thanks!

### Which category does this issue belong to?

_No response_

### What underlying problem are you trying to solve with this feature?

_No response_

### Which operating system are you running Bazel on?

_No response_

### What is the output of `bazel info release`?

_No response_

### If `bazel info release` returns `development version` or `(@non-git)`, tell us how you built Bazel.

_No response_

### What's the output of `git remote get-url origin; git rev-parse HEAD` ?

```text

```

### Have you found anything relevant by searching the web?

_No response_

### Any other information, logs, or outputs that you want to share?

_No response_

Review the behavior change in PR 28810 and trace the include-verification handling for the proposed common --windows_include_verification_case_insensitivity option. Check how the Windows and Linux cases are tested, and consider the work complete when Windows users can configure whether mismatched include-path and filename casing is reported.

Written by the indexing model from the issue text.