This reverts commit 562a35fd, reversing
changes made to 4a78b412.  This was
done because we inadvertently merged a good chunk of master when
patch a96b9edc was submitted to the v0.6 branch.  We will
cherry-pick a96b9edc

 in a later patch to restore the fix
in the proper way.

Change-Id: Ib16c0220e65697a68a5140960b82780c175d9fa2
Signed-off-by: Greg Haskins <gregory.haskins@gmail.com>

These changes make sure that the logging.chaincode setting from
core.yaml is used to set the chaincode logging level every time
the chaincode container starts. The peer reads in the value and
passes it to the chaincode via an environment variable as it
does for similar values.

Fix Issue FAB-394

Change-Id: Ic4b7228c57fc673a97dbfafc1b086ad04c41c05c
Signed-off-by: Will Lahti <wtlahti@us.ibm.com>

Replaced ChaincodeStub with ChaincodeStubInterface to allow
unit testing of chaincode. MockStub added to emulate a real
chaincode without the storage or network requirements.
Unit test examples for chaincode_example02 to 05.

I have another changeset to address tables and certificates.

Change-Id: I37d6115781436e080a70d5c48c1128ee01fef3ba
Signed-off-by: Bradley Gorman <bgorman@au1.ibm.com>