docs: update Cactus naming to Cacti across documentation pages

[abhigyan1102]

Description

Follow-up to #4197. Continues the documentation audit by updating remaining
"Hyperledger Cactus" references to "Hyperledger Cacti" across documentation pages.

Part of the Cacti Cleanup Initiative (goal #4: Improve documentation).

Changes (12 files, 39 lines)

• introduction.md — Updated project name, "What is Cacti?", "Why use Cacti?" sections
• governance.md — Updated naming, fixed repo URLs, updated RocketChat → Discord
• examples.md — Updated naming in nav links
• packages.md — Updated component section title
• support.md + support/*.md — Updated version references across all 5 ledger support pages (besu, corda, fabric, xdai, substrate)
• whitepaper.md — Updated title
• regulatory-and-industry-initiatives-reading-list.md — Updated nav links

Related

• Previous PR: docs: update outdated pre-merger references in contributor documentation #4197
• Cacti Cleanup Initiative: Cacti cleanup
• Mentorship Issue: Improve usability, maintainability, and contributor experience of Hyperledger Cacti LF-Decentralized-Trust-Mentorships/mentorship-program#62

[sandeepnRES]

Please squash the commits into single commit.

[abhigyan1102]

done, squashed into single commit and resolved the merge conflict

[VRamakrishna]

Thanks for this effort. FYI, Cacti is still largely Cactus+Weaver (i.e., an aggregation of two older systems). So it may make sense to retain the "Cactus" label in several docs, like in the ones talking about the various connector specs. There is an integration roadmap (see ROADMAP.md in the root folder) but it's very much a long-term WIP.

@RafaelAPB What's your opinion on this? Are you fine with renaming Cactus to Cacti globally, even for Cactus-specific code and docs? Note that several package names (for connectors and APIs) still retain the cactus- prefix.

('ll unblock my request for changes once we've resolved this.)

[abhigyan1102]

Thanks @VRamakrishna — that's a fair point. I'll hold off on
further changes until @RafaelAPB weighs in on the scope.

If the consensus is to keep "Cactus" for component-specific
docs (connector specs, APIs with cactus- prefix), I can
revise this PR to only update the project-level references
(introduction, governance, whitepaper) while preserving
"Cactus" in component-specific docs.

Happy to adjust either way.

[RafaelAPB]

@abhigyan1102 thank you for your contribution! @VRamakrishna I have no issue in changing the naming to Cacti. That is the roadmap and I don't think there's a lot of value in discriminating the name "cactus" to indicate it is a package pre-merge.

[AndreAugusto11]

@abhigyan1102 thank you for your contribution. Could you please squash the commits into a single one so that we can merge after @VRamakrishna's feedback?

[abhigyan1102]

alright i will do it @AndreAugusto11

[VRamakrishna]

LGTM, but please fix a couple of Hyperledger -->LFDT references I've pointed out before merging.

[abhigyan1102]

@VRamakrishna alright i will fix this one