Unable to check result 'undefined' in cli
add ReadResourceWithRuntimeResourceTestCase

The test clarifies the current behaviour of
invoking :read-resource(include-runtime=true,recursive=true)
with no actual runtime resource.
[WFCORE-179] Removed deprecated TransformationContext.resolveExpressions()
[WFCORE-179] Support nested expression in management expression resolution
[WFCORE-280] Respect expression escaping even when recursive expressions are involved
[WFCORE-57-fix-update] : Fix for WFCORE-57
The changes in the ReadResourceDescriptionHandler weren't in the ReadResourceHandler creating a difference in result :
  the read resource displaying aliases which were filtered out by the read resource description.
Fixing not-equals and path-does-not-exist bugs.
Merge pull request #367 from ehsavoie/WFCORE-57-fix-update

[WFCORE-57-fix-update] : Fix for WFCORE-57-fix
Merge pull request #361 from jmesnil/read-resource_with_runtime_resource

add ReadResourceWithRuntimeResourceTestCase
Merge pull request #359 from Gonthim/master-cli-undefined

Unable to check result "undefined" in cli
Merge pull request #358 from bstansberry/WFCORE-179

[WFCORE-179] Support nested expressions in management expression resolution