feat: add ccapi to application samples

[osamamagdy]

What this PR does / why we need it:
This PR is a continuation to #779 on how to integrate with the cc-tools project, especially using the cc-tools-demo project

Here, we add the CCAPI, which is an API server that uses REST APIs to communicate with peers and invoke operations.

Which issue(s) this PR fixes:

Fixes the LFX mentorship project Hyperledger Fabric CC-Tools Support for Fabric Private Chaincode

[munapower]

@osamamagdy checks are failing because you have to add core_peer_org_name to the test.sh script in the test-network directory around line 111
you also have to update the cc-tools-demo readme because it is missing the same definition that you did add to the test-network readme.
For some reason when I started the chaincode I got this error:

EGo (bundled) v1.5.3 (04243b39cc7bdc92732c2dacca8c509f8fb10550)
2025-01-22 20:32:09 panic: signal: illegal instruction
2025-01-22 20:32:09 
2025-01-22 20:32:09 goroutine 1 [running]:
2025-01-22 20:32:09 main.main()
2025-01-22 20:32:09     github.com/edgelesssys/ego/ego/cmd/bundle/main.go:58 +0x155
2025-01-22 20:32:05 [erthost] running in simulation mode
2025-01-22 20:32:05 [erthost] loading enclave ...

[mbrandenburger]

@osamamagdy checks are failing because you have to add core_peer_org_name to the test.sh script in the test-network directory around line 111 you also have to update the cc-tools-demo readme because it is missing the same definition that you did add to the test-network readme. For some reason when I started the chaincode I got this error:

EGo (bundled) v1.5.3 (04243b39cc7bdc92732c2dacca8c509f8fb10550)
2025-01-22 20:32:09 panic: signal: illegal instruction
2025-01-22 20:32:09 
2025-01-22 20:32:09 goroutine 1 [running]:
2025-01-22 20:32:09 main.main()
2025-01-22 20:32:09     github.com/edgelesssys/ego/ego/cmd/bundle/main.go:58 +0x155
2025-01-22 20:32:05 [erthost] running in simulation mode
2025-01-22 20:32:05 [erthost] loading enclave ...

It seems that you run it with ego instead of pure go (for testing on M1).

[mbrandenburger]

Looking at the Github actions ... it's still failing related to the missing CORE_PEER_ORG_NAME when running the simple-cli. See here https://github.com/hyperledger/fabric-private-chaincode/actions/runs/12829555830/job/35985706439?pr=780#step:7:10333

[munapower]

@osamamagdy checks are failing because you have to add core_peer_org_name to the test.sh script in the test-network directory around line 111 you also have to update the cc-tools-demo readme because it is missing the same definition that you did add to the test-network readme. For some reason when I started the chaincode I got this error:

EGo (bundled) v1.5.3 (04243b39cc7bdc92732c2dacca8c509f8fb10550)
2025-01-22 20:32:09 panic: signal: illegal instruction
2025-01-22 20:32:09 
2025-01-22 20:32:09 goroutine 1 [running]:
2025-01-22 20:32:09 main.main()
2025-01-22 20:32:09     github.com/edgelesssys/ego/ego/cmd/bundle/main.go:58 +0x155
2025-01-22 20:32:05 [erthost] running in simulation mode
2025-01-22 20:32:05 [erthost] loading enclave ...

It seems that you run it with ego instead of pure go (for testing on M1).

yeah @mbrandenburger now that you mention it I remember!

[munapower]

I was able to make it run ....

[mbrandenburger]

LGTM