Add an utility for stack trace analysis

The tool is supposed to find all remote class paths and create a file
named "not-reportale" containing a short explanation why the examined
stack trace is not reportable via ABRT.

The tool is designed for usage in post-create event.

Related to #29
Hook the stack trace analysis tool in post-create

Related to #29
Add abrt-action-analyze-java to the spec file

Related to #29
Add test for analysis tool

Related to #29
Use satyr for calculation of the duplicates hashes

The current algorithm simply hashes the entire backtrace file. This
approach results in non-working deduplication because the duplicate hash
depends on file system paths and line numbers.

Satyr provide a function for generating of reliable hashes where only
function names (in case of Java it means exception type too) are used
for input of the hash function.

Related to #29
Add a manual page for the analysis tool

Related to #29
Add the analysis tool's manual page to the spec file

Related to #29
Merge pull request #32 from jfilak/gh29_not_reportable

Introduce abrt-action-analyze-java