Don't use simply "hedera" as package name

[Neurone]

Problem

We often use hashgraph (package) and sdk (name), i.e., @hashgraph/sdk, com.hedera.hashgraph/sdk, github.com/hashgraph/hedera-sdk-go/v2, to name other SDKs. With C++ and Rust we use simply the Hedera/hedera namespace for the SDK package. I found both hashgraph and hedera on crates.io, but the hashgraph package seems outdated. For other packages we uses hedera-SOMETHING (i.e., hedera-proto). The situation is a bit confusing, and keeping just "hedera" or "hashgraph" I assume can create problems in the future.

Solution

• use hashgraph-sdk as package name
• (optionally) use hedera-sdk if we think this new naming convention is the correct one (and we should ask other SDKs to fix their naming convention accordingly)

Alternatives

No response

[mehcode]

Hashgraph is not Hedera. The name "Hedera Hashgraph" or "Hashgraph Hedera" or just "Hedera" should all be fine. For JS, someone is squatting on the hedera name or it would have been that.