[ADD] Add feature - visualization of text analaysis results and wo steps

[kostobog]

This pull request introduces several changes

1. Extends JOPA model adding

• TaskStepPlan.java step parts of TaskPlan class.
• FailureAnnotation.java as field of TaskStepPlan referring to the annotation result.

2. Implements a DAO and layer to read TaskStepPlan and FailureAnnotation data from the repository.
3. Implements Service layer logic to attach TaskStepPlan with FailureAnnotations to TaskPlans when constructing a RevisionPlan, see AircraftRevisionPlannerService method createRevisionPlanScheduleDeducedFromSimilarRevisions.
4. Refactors JOPA model

[blcham]

LGTM, although I would wait for text analysis from Matej and refactor this pull request according to it

[blcham]

LGTM, can be merged.

[blcham]

I suggest removing irrelevant lines like this one.

[kostobog]

This pull request contains queries to compute the component failure classes of work order executions. Each work order execution has one or more steps and each step has work order text in which failure component terms are annotated. Each work order text is annotated with one component and its failure failure terms. Component classes are created as follows:

• cm:component-failure--task - for each work order execution an ordered list is created where elements in the list are constructed from execution step index and its component and failure terms. The list is ordered by the step index and it is hashed with MD5. The hash is used to construct the IRI that represents the component class failure. See query construct-component-failure-class.sparql

Alternatively the work order execution classes can be created without using the index. There are two alternatives which can be analyzed.

• one alternative is to create the hash from the ordered list of component failure pairs of the steps of the task execution.
• second alternative is to create the has from a set of component failure pairs of the steps of the task execution.