docs(examples/supply-chain-app): print correct web host in the CLI logs

[petermetz]

1. The logs were showing the bound host which in our case was 0.0.0.0
   but that is not accepted by web browsers when you are executing HTTP XHR
   requests from Javascript.
2. This change makes it so that even though we bind to 0.0.0.0 the logs
   to the person running the example application will show 127.0.0.1.
   This might potentially cause further confusion in some people who'd think
   that we are binding to 127.0.0.1 based on the logs, but this seems like an
   acceptable trade-off for an example which has the number one priority of
   being easily digestable.

Fixes #2390

Depends on #3362

Signed-off-by: Peter Somogyvari peter.somogyvari@accenture.com

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.

[github-actions]

This PR/issue depends on:

• hyperledger/cacti#3362
  By Dependent Issues (🤖). Happy coding!