windows: Add build verification step to ensure path lengths

The Windows path length limit is 260 characters and can potentially be exceeded as seen in https://github.com/envoyproxy/envoy/pull/10560. The compiler error emitted when the max path length is exceeded does not point to the actual problem by outputting `No such file or directory`. It is unclear if this is the only behavior.

Ideally, there would be an explicit check for these path lengths during the Windows build and failure output that clearly indicates the problem.