docs: change github org from hyperledger to hyperledger-cacti

[petermetz]

The diff here came to be by doing a simple search & replace repo-wise where "https://github.com/hyperledger/cacti/" got replaced with "https://github.com/hyperledger-cacti/cacti/"

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

Pull Request Requirements

• [x] 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.
• [x] 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.
• [x] Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

• [x] Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
• [x] 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.

[VRamakrishna]

@petermetz If Ry is going to add a redirect from github.com/hyperledger/cacti to github.com/hyperledger-cacti/cacti, are these changes still required?

I'm asking because we intend to (at some point) migrate the repo over again to the lf-decentralized-trust organization, right?

Otherwise, changes LGTM.

[petermetz]

@petermetz If Ry is going to add a redirect from github.com/hyperledger/cacti to github.com/hyperledger-cacti/cacti, are these changes still required?

I'm asking because we intend to (at some point) migrate the repo over again to the lf-decentralized-trust organization, right?

Otherwise, changes LGTM.

@VRamakrishna I'd say regardless of what happens in the near future, it's best to keep the docs links as up to date as possible to demonstrate project liveness. The redirections could end up being turned off later through some unintended side-effect of a configuration change. I'm happy to send another PR if/when we migrate to the LFDT org.