Support configurable suppression of compact and full stack trace

[aryoda]

Not everybody wants to see the full or compact stack trace (or any at all) in case of thrown conditions. The condition message may be enough.

Add a possibility to control the suppression of the compact and full stack trace (one of them or both or none).

Related to issues

• Logging: Suppress empty compact stack trace output #5 (Suppress empty compact stack trace) and
• Add an option for the default value of the build.log.output argument include.full.call.stack #25 (Add option for include.full.call.stack)

[aryoda]

Implementation proposal:

Add two more arguments to the tryCatchLog and tryLog functions:

1. suppress.compact.stack.trace
2. suppress.full.stack.trace

The default values are fetched from the R options (eg. suppress.full.stack.trace = getOption("tryCatchLog.suppress.full.stack.trace", TRUE)).

Open questions:

1. Does it make sense to allow different suppression settings for each condition type (error, warning, message...)? This would span a configuration "matrix".

2. Are there other possible settings beyond suppression (eg. "show only the exact location without a call stack...")? Then the arguments should have a different name (not "suppress.*") and be of type string. How to specify the allowed setting values then? Via base::match.arg functionality?

[aryoda]

tryCatchLog and tryCatch now have two additional arguments named
include.full.call.stack and include.compact.call.stack which can also be configured globally
via options.

Unit tests are still missing. Merging back of the feature branch #44 into master will be done after success unit tests...