Old question, but for other people facing the same issue:

Since Windows 10 1803, it is possible to set certain folders as case-sensitive in windows.

You can use this command:

fsutil file setCaseSensitiveInfo <folder_path> enable

This only works on empty folders, so you might have to create a new folder and then move all the existing files, but it can avoid issues like this.
It obviously does not solve the issue exactly, but the only real solution is to fix the file names anyway in this case rather than trying to make it work with some hacky solution.

By setting the case sensitivity you get the added bonus that you can't accidentally have a version that works locally, but not on prod