Wire release pipeline to crates.io, PyPI, and npm

On every v* tag push the release workflow now publishes the project to
all three public registries in parallel:

- crates.io: wickra-core then wickra-data then wickra, with a 45-second
  sleep between each so the registry index can refresh before the next
  publish step asserts the previous version is available.

- PyPI: maturin-action builds wheels for Linux x86_64 + aarch64, macOS
  x86_64 + aarch64, and Windows x64, plus an sdist; all artefacts upload
  to PyPI via MATURIN_PYPI_TOKEN.

- npm: napi-rs builds a native binary per platform (linux-x64-gnu,
  darwin-x64, darwin-arm64, win32-x64-msvc), publishes each as its own
  platform package, then publishes the main `wickra` meta-package
  that resolves to the right platform at install time.

- WASM: wasm-pack builds the bundler-target package and publishes it as
  `wickra-wasm` on npm, with the auto-generated package.json enriched
  with the author/repo/license metadata.

Package metadata was unified so all targets point at kingchenc/wickra
on GitHub; the Node binding is now plain `wickra` (the @wickra/ scope
was unnecessary because the bare name was free). README install table
updated to match.

bindings/python/pyproject.toml

@@ -45,9 +45,9 @@ bench = [
 ]
 
 [project.urls]
-Homepage = "https://github.com/wickra/wickra"
-Repository = "https://github.com/wickra/wickra"
-Issues = "https://github.com/wickra/wickra/issues"
+Homepage = "https://github.com/kingchenc/wickra"
+Repository = "https://github.com/kingchenc/wickra"
+Issues = "https://github.com/kingchenc/wickra/issues"
 
 [tool.maturin]
 manifest-path = "Cargo.toml"