Updates to test chaincode to exploit new microfab

[bestbeforetoday]

New microfab version provides an up-to-date Gradle version, which the test chaincode can be updated to exploit.

This change also updates several dependencies to current versions.

This change required hyperledger-labs/microfab#174. The version of Gradle contained in microfab v0.0.19 is too old to support current versions of the Gradle shadowJar used in this change for the bare Gradle chaincode tests.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[denyeart]

Note that my fabric-samples test against latest microfab failed - https://github.com/hyperledger/fabric-samples/actions/runs/12055602173. I haven't yet looked into the reason...

[bestbeforetoday]

I just tried running the full-stack-asset-transfer sample manually using latest fabric-samples, Fabric v3.0.0 and microfab:0.0.20. I can bring up microfab, deploy the chaincode (as a service), start the chaincode process locally, then run the client application OK. I'm not sure what hasn't worked with the test run.

I am running the chaincode with npm run start:server-debug, as per the workshop instructions. The test looks to be running as npm run start:server-nontls. I'm not sure if that could be a difference, or perhaps just timing-related.

[bestbeforetoday]

@denyeart fabric-samples fix in hyperledger/fabric-samples#1272.

This PR is building OK and should be ready to merge. I'll see if a similar fix to the one in fabric-samples is appropriate for this repo and, if so, deliver it in another PR.

[denyeart]

Thanks Mark!