Refactor policy evaluation response to allow different levels of embedding values

This commit changes two things:

• evaluationID is no longer returned as part of the JSON response, but instead is returned as HTTP ETag header
• if policy source code contains a single blank variable assignment then the result from the policy evaluation will be only the value of that variable

Closes #33 (closed)

@yordan.kinkov @valerii.kalashnikov