[feat] Add configuration parameter for automatically capturing command errors and exit code in job scripts

[jgphpc]

Will fix #1196

[codecov-commenter]

Codecov Report

Merging #1490 into master will increase coverage by 0.07%.
The diff coverage is 96.77%.

@@            Coverage Diff             @@
##           master    #1490      +/-   ##
==========================================
+ Coverage   91.65%   91.72%   +0.07%     
==========================================
  Files          83       83              
  Lines       13012    13029      +17     
==========================================
+ Hits        11926    11951      +25     
+ Misses       1086     1078       -8     

Impacted Files	Coverage Δ
reframe/core/pipeline.py	92.87% <88.88%> (+0.06%)	⬆️
unittests/test_pipeline.py	95.19% <100.00%> (+1.19%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f8889c9...a252634. Read the comment docs.

[vkarak]

We will also need a unit test.

[victorusu]

Does it make sense to allow the check to bypass this configuration? Something like

self.trap_job_errors = False

The use case is when one needs to write a check where one expects a command to exit code different than zero, while the default config is set to trap_job_errors=True.
In this case, this check cannot be executed together with other checks, it needs a different ReFrame invocation.

[vkarak]

@victorusu I would see it as a job parameter rather than a test parameter. I'm generally against bloating either API, though, unless we need to. If that comes as a feature request from a real scenario, then we can discuss it again.

[vkarak]

lgtm now