Explain github dependancies and best practices

[nuke-web3]

We need a dedicated place on devhub outlining how to navigate "dependency hell" in Substrate, as versioning is the primary issue for most if you are not careful.

• Reminder of how to specify properly in cargo.toml (git, tag, rev, branch, etc.) and not to manually update Cargo.lock. But scan the lockfile for multiple versions of the same deps (need to fix this with cargo update after setting version & deps repo correctly)
• How to set upstream deps for substrate to match a 3rd party pallet's (or better, the opposite)
• How to identify version issues and resolve them with https://doc.rust-lang.org/cargo/commands/cargo-update.html#examples cargo update -p foo --precise 1.2.3
• {more?}

[dkrizhanovskyi]

Hello! I would like to contribute to this task by creating detailed documentation on managing dependencies in Substrate projects, including best practices for working with Cargo.toml and Cargo.lock. I plan to cover dependency versioning issues and provide guidelines on updating dependencies with cargo update. Please let me know if you have any specific requirements or suggestions before I start.

Thank you!