Work around write-file-atomic Windows EPERM issue

[coreyfarrell]

Fixes #14

---

Going to wait for more feedback from @ehmicky to verify this resolves the issue before I consider merging. Just posting the PR so it becomes visible to others in case someone objects to using a retry cycle. My thinking is that caching-transform success implies that the cache file has been successfully created.

[coveralls]

Pull Request Test Coverage Report for Build 61

• 12 of 12 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 58:	0.0%
Covered Lines:	50
Relevant Lines:	50

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 63

• 12 of 12 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 58:	0.0%
Covered Lines:	50
Relevant Lines:	50

---

💛 - Coveralls

[coreyfarrell]

@ehmicky has stated that this fixes testing on Windows. Anyone have feelings for/against this approach to fixing the issue? @bcoe @JaKXz?

[bcoe]

@coreyfarrell this is definitely a little icky 😄

I'll 👍, but is there a tracking issue on the Node.js project for this regression?

[coreyfarrell]

To my knowledge it's not a node.js regression. See npm/write-file-atomic#28.

[coreyfarrell]

@JaKXz I'm leaving the unbreak-windows branch in place for now, it looks like @ehmicky is installing from that branch.

@ehmicky please point your package.json directly to 1689877 (the commit merged to master for this PR). At some point the unbreak-windows branch will be deleted. Edit: be sure to point at the specific SHA and not the master branch. At some point soon and without warning master will get a version bump and npm will not allow the bumped version to be used by nyc@14.

[ehmicky]

Thanks for checking it! I've changed the reference to point to the commit hash, you can now safely remove the unbreak-windows branch. It's not used in production by anyone anymore.