Replacment of - vs _ in package names inconsistent

[nuke-web3]

In the docs the behavior of replacement of dashes (-) vs underscore (_) is not as described. See bytecodealliance/cargo-component#250 (comment) for details.

Seems related to:
Overall I've always found the lib.name key to be super confusing because it adds to the dashes-vs-underscore ambiguity, which sometimes crops up with crates which use dashes in package.name and underscores in lib.name and while that kind of works it doesn't always work because now you need to use lib.name for specifying patches.

Originally posted by in #6827 (comment)