feat: better error reporting

[erdos]

Make error messages more readable to help users. Tasks:

• Generalize the use of EvalException and ParsingException. The Stencil API should throw only these two exceptions (and IOException in some cases).
• Define a set of most common error cases
• Add integration tests to check that meaningful error messages are displayed
• Make sure meaningful error messages are propagated to the response in the service

Related to #139

Testing

Run locally with Leiningen as:

$ lein run path-to-template-docx-file path-to-a-json-payload-file

In case of error, process returns error code 4 and prints the improved error message (same that would be returned by the service).

[codecov]

Codecov Report

Merging #140 (6633947) into master (a7dc048) will increase coverage by 0.23%.
The diff coverage is 90.47%.

@@            Coverage Diff             @@
##           master     #140      +/-   ##
==========================================
+ Coverage   92.03%   92.26%   +0.23%     
==========================================
  Files          26       26              
  Lines        1895     1900       +5     
  Branches      106      105       -1     
==========================================
+ Hits         1744     1753       +9     
+ Misses         45       42       -3     
+ Partials      106      105       -1     

Impacted Files	Coverage Δ
src/stencil/infix.clj	88.39% <60.00%> (+1.10%)	⬆️
src/stencil/cleanup.clj	95.31% <100.00%> (+1.56%)	⬆️
src/stencil/eval.clj	97.36% <100.00%> (+0.22%)	⬆️
src/stencil/merger.clj	99.07% <100.00%> (+0.01%)	⬆️
src/stencil/model.clj	96.89% <100.00%> (-0.04%)	⬇️
src/stencil/tokenizer.clj	96.77% <100.00%> (ø)
src/stencil/util.clj	95.50% <100.00%> (+0.10%)	⬆️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more