Coverage path length issue

Hi

So recently migrated over to this package, and since we have a mono-repo of a front-end, which includes multiple different path and sometimes a few nested components. When trying to view a coverage report, I came across this error:
After some investigations I found out the problem was to do with the path character length, which exceeded 260 characters (excluding the `file://C:/Users/` Is there a way to possibly take this length into consideration? Not sure how many people would be affected by this, but you wouldn't be able to view the reports on any browser because of the limit. See below a link for windows length limits
[Windows path limit](https://learn.microsoft.com/en-us/windows/desktop/FileIO/naming-a-file#maximum-path-length-limitation)

Here is a stackoverflow explaining it more: [stackOverflow](https://stackoverflow.com/questions/1880321/why-does-the-260-character-path-length-limit-exist-in-windows)

No source file or test is named. Start by locating the coverage report generation and browser report path handling in karma-coverage, then reproduce the issue with a Windows path exceeding 260 characters. Done means coverage reports remain viewable in a browser for the long-path scenario.

Written by the indexing model from the issue text.