Publish chain-spec-builder (#4518)

marking it as release-able, attaching the same version number that is
attached to other binaries such as `polkadot` and `polkadot-parachain`.

I have more thoughts about the version number, though. The chain-spec
builder is mainly a user of the `sp-genesis-builder` api. So the
versioning should be such that it helps users know give a version of
`sp-genesis-builder` in their runtime, which version of
`chain-spec-builder` should they use?

With this, we can possibly alter the version number to always match
`sp-genesis-builder`.

Fixes #4352

- [x] Add to release artifacts ~~similar to
#4405 done here:
#4557

---------

Co-authored-by: Branislav Kontur <bkontur@gmail.com>

substrate/bin/utils/chain-spec-builder/Cargo.toml

@@ -1,14 +1,14 @@
 [package]
 name = "staging-chain-spec-builder"
-version = "0.1.0"
+version = "1.6.0"
 authors.workspace = true
 edition.workspace = true
 build = "build.rs"
 license = "GPL-3.0-or-later WITH Classpath-exception-2.0"
 homepage = "https://substrate.io"
 repository.workspace = true
-publish = false
-description = "staging-chain-spec-builder (polkadot v1.12.0)"
+publish = true
+description = "Utility for building chain-specification files for Substrate-based runtimes based on `sp-genesis-builder`"
 
 [lints]
 workspace = true