Add pipeline for upload matter-rs crates to crates.io about rs-matter HOT 2 OPEN

@kedars This means a decision needs to be taken as to what would be the name under which the matter crate in the matter-rs workspace will be published/known in crates.io. To remind us about the status quo:

• matter is already taken by a parser/formatter library
• matter-rs is already taken by an empty project which seemingly just reserved the matter-rs name and nothing else
• matter-iot is available (but maybe a bit longer?)
• Other options:
  • matters (kind of a short-cut of matter-rs and a play with words :) )
  • chip (the old name of the Matter project - why not?)
  • chip-rs

In any case, and whatever name you pick, ideally we need to rename the matter crate in the matter-rs workspace to a new name, so that the crate name in the workspace and its crates.io name do match. While not strictly required, I think keeping two different names is confusing. For one, the examples would refer to the workspace crate name, while users would need to use the crates.io name and just copy-pasting the examples won't work 1:1 (in that users would either need to rename the crates.io crate name in Cargo.toml's [dependencies] section back to matter for the examples to work out of the box, or they'll need to adjust the use statement when pasting the example code. Both things quite annoying).

from rs-matter.

Yes, this will happen soon enough. Depending upon the crypto, both the mbedtls and openssl, couldn't be run out of the box using their respective crates and required some patches in the Git repos. But the rust-crypto is cleaner.

from rs-matter.