Formatting warnings/errors from glslc so VS can process them in the Errors/Issues List

The formatting of errors, means that VS can't jump to them. Having to scour the build errors instead of a summary list isn't fun. Ideally VS should take in both of these styles, but doesn't.

VS wants errors formatted like this. Clang-cli and MSVC also format this way. So that's all VS intercepts.

```
1>Data/Shaders/LumFeedback.vert(65): error: 'setPointSize' : no matching overloaded function found

1>Data/Shaders/LumFeedback.vert(65,1): error: 'setPointSize' : no matching overloaded function found
```

But glslc formats them on Windows like this. This is how mac/linux clang format errors.

```
1>Data/Shaders/LumFeedback.vert:65: error: 'setPointSize' : no matching overloaded function found
```