Add cargo install method to installation documentation

[nuke-web3]

I see that it's possible to run locally without needing docker or homebrew etc. for those using the Rust toolchain natively:

tabby/CONTRIBUTING.md

Lines 48 to 54 in b71f9c5

	## Building and Running
	Tabby can be run through `cargo` in much the same manner as docker:
	```
	cargo run serve --model TabbyML/StarCoder-1B
	```

Would https://tabby.tabbyml.com/docs/installation/ be open to a PR that echos the CONTRIBUTING doc on how to install and run directly? Or is there something more nuanced about how the binary / container is shipped that doing this would miss?

[nuke-web3]

Also maybe a minor nit: I see it's suggested to use cargo run in debud more, not cargo run --release - is that intentional?

[wsxiaoys]

The CONTRIBUTING.md file serves as a guide for those interested in contributing to the development of Tabby. It is not intended for general users who wish to deploy or run Tabby on their infrastructure.

The container and binary are distributed at the following locations:

• https://github.com/TabbyML/tabby/releases/tag/v0.10.0
• https://hub.docker.com/r/tabbyml/tabby

[nuke-web3]

It is not intended for general users who wish to deploy or run Tabby on their infrastructure.

Is there a specific reason why? As my intended use is to run and use the service only on a single device, and would much rather have a compiled from source version to do that than a bin/container. With #2035 I can get this running in --release mode just fine, TBD soon if the API exposed at the default 0.0.0.0:8080 is working correctly.

[wsxiaoys]

for local use case, why not just using the binary distribution / docker distribution linked above?

[nuke-web3]

I do not run untrusted binary distributions whenever possible. As I mentioned I want to build from source. Especially when it's a cargo project that makes it very easy! 😁 (Minus the require intalled deps as I ran into here 😅 )