Fix open window association with --disable-features=nw2

[McGiverGim]

The opening of a more than one Blackbox windows when double click on the blackbox log file is broken.

The Chrome compatibility is hitting us again...

If was broken here #456 when we disabled de features of nw2 because the export video was broken in #450

I have returned to the old code and now it works. But we need to remember to revert this when we remove the nw2 disable parameter.

Another fast solution for this problem is to modify the export video code here:

blackbox-log-viewer/js/flightlog_video_renderer.js

Lines 91 to 93 in bbd9a7b

	function supportsFileWriter() {
	return !!(chrome && chrome.fileSystem);
	}

Adding a !isNW() to the condition, but this makes the video to be loaded into memory before exporting. I think is better to write directly to disk.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities (and 0 Security Hotspots to review)
0 Code Smells

No Coverage information
0.0% Duplication

[McGiverGim]

Only as information: there have been several updates to the library we are using here: https://github.com/thenickdude/webm-writer-js and there is one sample of using it with node, so maybe there is a better solution. I simply didn't have time to look into it.

[mikeller]

This is turning into a game of whack-a-mole around NW2 features - I think we should look into cutting the chase, and do the (considerable) changes to move our apps to NW2, or else look for a new framework to move to - trying to stay in Chrome / NW1 is not going to become less tedious as time goes by.