Create a rust code style guide for the repository

[chefsale]

We should have a style guide for the rust codebase.

• [ ] use husky to run pre-commit checks - pre-commit checks include: run cargo format - 1h
• [x] use short qualified names - use cargo format to make sure used names are following convention - 1h
• [ ] cargo command for death code check - detect orphans https://crates.io/crates/cargo-modules - include in husky
• [x] use tests in a separate file than source code (update existing 48 tests) - update 1h
• [x] check if there is lint rule to avoid having tests in source code file - https://rust-lang.github.io/rust-clippy/master/index.html#/tests_outside_test_module - include in husky - included estimation above

Create document to explain style guide - 3h

• [ ] mention above rules
• [ ] explain rule: if there is an enum variant with value, we should use a kind object

Risk factor:

• husky - 2h

[fbozic]

We need to define how to build server interfaces so they are user-friendly in both Rust and Typescript.

[MatejVukosav]

Ideas for more clippy rules: https://github.com/danwilliams/standards-rs?tab=readme-ov-file#code-linting @miraclx go through and see what we can include