feat(rust/signed-doc): add binary compilation

[cong-or]

The following produces an ELF binary in the target after a release build.

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 272/272}$ | ${\color{red}Fail: 0/272}$ |

[stanislav-tkach]

I don't think it is an issue, but now I'm getting the following warning:

warning: .../catalyst-libs/rust/signed_doc/Cargo.toml: file .../catalyst-libs/rust/signed_doc/examples/mk_signed_doc.rs found to be present in multiple build targets:

• bin target signed-docs
• example target mk_signed_doc

Maybe we should remove it from the examples if this binary is generally usable?..
@Mr-Leshiy

[cong-or]

I don't think it is an issue, but now I'm getting the following warning:

warning: .../catalyst-libs/rust/signed_doc/Cargo.toml: file .../catalyst-libs/rust/signed_doc/examples/mk_signed_doc.rs found to be present in multiple build targets:

• bin target signed-docs
• example target mk_signed_doc

Maybe we should remove it from the examples if this binary is generally usable?.. @Mr-Leshiy

@stanislav-tkach we need the binary for the load tester which is written in python. We could revert it and I can use a branch instead.

[stanislav-tkach]

@cong-or It is just a warning, so we can ignore it. I think that more convenient testing is more important, but I would like to hear other opinions.