Add Robustness Information in Documentation

[mhellmeier]

🚀 Feature Request

Current Problem

The robustness problem is described in the upstream issue #20.

Proposed Solution

Update Trendmark documentation with recommendations for robustness (for example, suggest using the SizedCRC32Watermark if robustness is important and mention the trade-offs).

Additional Context

Comment from @hnorkowski:

Further analysis methods could be implemented as static method in Trendmark. The extracting methods of (Jvm)Watermarker could be extended by another parameter trashing: Bool that defines if all Trendmarks which produce an error or warning are thrown away.