feat(manifest): complete the manifest of all published libraries

[clearloop]

Resolves #2940
part of #2923
split from #2924

complete the manifest of for all published libraries

status	package	categories	keywords
✅	common	wasm	gear, wasm
✅	common-codegen	wasm	gear, wasm, codegen
✅	core-backend-codegen	wasm	gear, wasm, codegen
✅	core-backend-common	wasm	gear, wasm
✅	core-backend-wasmi	wasmi	gear, wasm, wasm-executor
✅	core-errors		gear
✅	core-processor	wasm	gear, wasm
✅	core	wasm	gear, wasm
✅	gcli	command-line-interface, command-line-utilities, wasm	gear, cli, wasm
✅	gclient	api-bindings, wasm	gear, sdk, api
✅	gmeta	wasm	gear, wasm
✅	gmeta-codegen	wasm	gear, codegen
✅	gsdk	wasm, api-bindings	gear, sdk, api
✅	gsdk-codegen	api-bindings	gear, sdk, codegen
✅	gsys	wasm, api-bindings	gear, wasm
✅	wasm-instrument	wasm	gear, wasm

@gear-tech/dev

[StackOverflowExcept1on]

we can also fill the categories field in Cargo.toml
https://doc.rust-lang.org/cargo/reference/manifest.html#the-categories-field

For example, use wasm for executors and command-line-utilities for gcli.

[shamilsan]

I am not sure about the versions. It may be simpler to maintain when the version is the only one (in the workspace).

[clearloop]

I am not sure about the versions. It may be simpler to maintain when the version is the only one (in the workspace).

agree, I was considering that I may publish some dirty versions in the following PRs, so leaving some spaces for those operations, but it's actually okay to sync them since I can publish some alpha version at that time