Avoid stderr pollution from chrome/electron logging #132
Description
At this moment, while running tests, almost on any platforms, there are a series of notifications or warnings coming from chrome that cannot be addressed. These cannot really be addressed and they make reading the console considerably harder, especially as they are generated by a different process and they appear at random locations in output.
I investigated a redirection of stderr and it seems to be considerably improve the experience. Example of thing that no longer populated the console:
2022-03-03 09:10:37.800 Electron[55575:17722594] ApplePersistence=NO
2022-03-03 09:10:38.695 Code Helper (Renderer)[55583:17722698] CoreText note: Client requested name ".NewYork-Regular", it will get Times-Roman rather than the intended font. All system UI font access should be through proper APIs such as CTFontCreateUIFontForLanguage() or +[NSFont systemFontOfSize:].
2022-03-03 09:10:38.695 Code Helper (Renderer)[55583:17722698] CoreText note: Set a breakpoint on CTFontLogSystemFontNameRequest to debug.
(node:55731) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `Electron --trace-deprecation ...` to show where the warning was created)
[55580:0303/091046.311665:ERROR:gles2_cmd_decoder.cc(5004)] [.RendererMainThread-0x7f94b387e600]GL ERROR :GL_INVALID_FRAMEBUFFER_OPERATION : glDrawArrays: framebuffer incomplete
[55580:0303/091114.782105:ERROR:gles2_cmd_decoder.cc(5004)] [.RendererMainThread-0x7f94b387e600]GL ERROR :GL_INVALID_FRAMEBUFFER_OPERATION : glDrawArrays: framebuffer incomplete
I am not saying that we should sent this to /dev/null, just that we should dump it to an stderr.log instead, so it can be analyzed if really needed.