Feat: sgc --retry (closes #65)

[JPeer264]

@aichbauer any suggestions on how to test this?

[coveralls]

Coverage remained the same at 100.0% when pulling e895ec7 on feat/retry into b30c854 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling 04471dd on feat/retry into c6f7c0d on master.

[aichbauer]

Maybe you could make functions that read/writes the retry files and you call it in the cli.js so you have it separated from the cli input and then you could test if this function works properly?

Why are you rewriting some functions with async/await and others not?

[JPeer264]

Maybe you could make functions that read/writes the retry files and you call it in the cli.js so you have it separated from the cli input and then you could test if this function works properly?

Ya that would work.

Why are you rewriting some functions with async/await and others not?

Because top level await does not exist yet. And wrapping it into an own function would have been a little bit of an overhead. But ya maybe we should stick just either promises or async/await. Could rewrite it.

[JPeer264]

@aichbauer tests added 👍

[JPeer264]

I also did a little refactoring. Unfortunately it is in this PR, as it was too difficult to put it in another PR.

[aichbauer]

I will take a look into it as soon as possible.

[aichbauer]

LGTM