The ALISA plugin verification methods should call on methods returning AnalysisResult objects

[reteprelief]

Now that we have changed OSATE analyses to use AnalysiResult objects to return results, the Assure processor should call on them instead of the methods that return results through Eclipse markers.

[reteprelief]

Merged in #1468
Moves ExecuteJavaUtil to plugin support.
Introduces a first version of an extensionpoint to expose a Java class for external reflective invocation.

[reteprelief]

Includes new validation on verification activities to ensure that compute variables referenced in value predicates are assigned return values in the method call of the verification activity.

[reteprelief]

Merged in #1289
Assure now uses XMI to rather than XText to store Assure files.

[reteprelief]

Updated Result representation to remove nested Diagnostic.
Added separate attribute to record parameters in AnalysisResult
Added support for EObject and Java Object Values in Result.
Added DiagnosticType as type attribute to Result - done by making Result a subclass of Diagnostic.

[reteprelief]

Added method to ResultUtil that generates a URI for AnalysisResult resources. It reflects the target object in the resource name as well as the analysis name and a string value in the info attribute. The path is that in reports under the instances folder (the current organization).

[reteprelief]

AnalysisResult object returned by verification methods is now referenced by the verification activity result object. Assure takes its content into account for counts and for display navigation into the Result structure in the Assurance view.