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

changed milestone to %Sprint 10

added DevInProgress label

requested review from @tziai

assigned to @lyuben.penkovski

changed the description

removed review request for @tziai

added 4 commits

• bc554751...20a45ccd - 3 commits from branch main
• b6f8ad06 - Refactor policy evaluation response to allow different levels of embedding values

Compare with previous version

marked this merge request as ready

requested review from @tziai

changed the description

approved this merge request

@lyuben.penkovski approved

LGTM

added 3 commits

• b6f8ad06...648eed24 - 2 commits from branch main
• 53bd9486 - Refactor policy evaluation response to allow different levels of embedding values

Compare with previous version

added 3 commits

• 53bd9486...4dfe4ef4 - 2 commits from branch main
• 3955eec0 - Refactor policy evaluation response to allow different levels of embedding values

Compare with previous version

merged

mentioned in commit 189a6262