docs(examples/supply-chain): fix yarn --no-lockfile

[aldousalvarez]

Primary Changes

1. Removed examples/supply-chain-app/package.json and moved the other files to cactus-example-supply -chain-backend
2. Updated the docs to match the updated path of the supply-chain-app files to cactus-example-supply- chain-backend and the new steps on how run the latest supply chain app
3. Updated the code responses in connector-fabric from null to (0) based on the logs and responses while running the application.

Fixes #2721

Pull Request Requirements

• Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
• Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
• Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

• Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
• Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

[petermetz]

@aldousalvarez It crash-loops on my machine with the Fabric AIO container never coming online (attached logs).
Could you please also post your complete log output of the yarn start:example-supply-chain that shows that the app comes online successfully? Diffing that against my log file should tell us what is the difference (hopefully)
2024-01-20-cacti-supply-chain-example-not-working.log

[aldousalvarez]

@petermetz Yes, I have also experienced that scenario. And it is like that for the whole day for me and then when I try it the next day it is working and the Fabric AIO comes online and the supply chain application runs.

Maybe this can help, here are the steps that I do before running the supply chain app

1. docker system prune -a
2. docker system prune --volumes
3. npm run enable-corepack
4. npm run configure
5. yarn run start:example-supply-chain

and here below is the logs when the supply chain app is successfully online
yarn run start example supply chain logs.txt

[petermetz]

@petermetz Yes, I have also experienced that scenario. And it is like that for the whole day for me and then when I try it the next day it is working and the Fabric AIO comes online and the supply chain application runs.

Maybe this can help, here are the steps that I do before running the supply chain app

1. docker system prune -a
2. docker system prune --volumes
3. npm run enable-corepack
4. npm run configure
5. yarn run start:example-supply-chain

and here below is the logs when the supply chain app is successfully online yarn run start example supply chain logs.txt

@aldousalvarez Got it, thank you! It's not ideal, but a small step forward is not a bad move so let's merge this and then I'll try to work on fixing the supply chain app so that it actually works with the documented steps.