Change exchangePublishScript.sh to publish sample business policies to the cluster org

[bmpotter]

Since business policies can't be public, customers can't use the business policies from the IBM org, and generally can't even view them (because they don't usually have credentials in the IBM org). So change exchangePublishScript.sh to publish the sample business policies to the cluster org instead. You may have to add <cluster-name> as an argument to the script, because exchangePublishScript.sh may not have the right info to be able to query that, but the caller does.

I think the example business policies should have a constraint like openhorizon.example == helloworld (or cpu2evtstreams, etc.). That way the nodes that want to use it can just set this node policy property: openhorizon.example: helloworld

[t-fine]

PR I submitted for this: https://github.com/open-horizon/examples/pull/301

[bmpotter]

A couple of small updates are needed:

• [x] Since to have the deployment policies created, the cluster org needs to be passed as an arg, ensure the 4.1 KC documentation has them set CLUSTER_ORG and then uses the cmd:

curl https://raw.githubusercontent.com/open-horizon/examples/v4.1/tools/exchangePublishScript.sh | bash -s -- -c $CLUSTER_ORG

• [x] The script requires that EXCHANGE_ROOT_PASS be set, but doesn't seem to actually use it. Since in the KC instructions they have to set HZN_EXCHANGE_USER_AUTH with the root pw for the hzn exchange status cmd, just remove the requirement for EXCHANGE_ROOT_PASS in this script.
• [x] The line : ${EXCHANGE_ROOT_PASS:?} ${HZN_EXCHANGE_URL:?} ${HZN_EXCHANGE_USER_AUTH:?} should be after the parsing of the args, so someone can use -h to see the usage to see what's required
• [x] Cloning the examples repo in the current dir is a lot of files to put there, that won't get cleaned up if the script exits with an error. Might be better to clone it in /tmp/
• [x] To have echo output newlines (\n) correctly, need to add the -e flag
• [x] The final "success" msg should not include the work "error", because when users scan it quickly it can look like things failed.