Investigate node/fs module behavior as found in src/report/dashboard.js

[miha42-github]

Description

I believe that there is a potential bug in node.js filesystem module. This file is needed because otherwise the actual final of the two images that needs to be inserted into the docx file won't load. If we create a scratch file then it will. Essentially something is off with the last file created in a series of files, but the second to last file appears ok.

Obviously more testing is needed before we approach the node team with something half baked. Until then here are some observations:

1. Unless the file of a given name is present, even if zero bytes, the image data will not be put into the file. If the file name exists then everything works.
2. Again the last file in a series of files appears to be corrupted and cannot, for some odd reason, be read by the docx module and be inserted into a docx file. Yet when we look at the file system object within the file system it can be opened without any problems.

TODOs

1. Create a separate program that emulates what is done in the mrcli dashboard
2. Try on multiple OSes
3. Clearly document the steps and problem encountered
4. In the separate standalone program try using with and without axios use default http without