Improve try-runtime documentation
Try-runtime feature was added in #58 (closed) and fixed in #222 (closed).
The existing documentation in /doc/test/replay-block.md is outdated: it's using try-runtime as a subcommand when it was actually moved in a dedicated cli (see !256 (merged)).
See
- https://paritytech.github.io/try-runtime-cli/try_runtime/
- https://github.com/paritytech/try-runtime-cli
- https://docs.substrate.io/reference/how-to-guides/tools/use-try-runtime/
Try-runtime is all about battle-testing unreleased runtimes.
Instead of testing runtime straight on gdev network after release we could first test it locally before releasing.
This could be a time gain when debugging: https://forum.duniter.org/t/gdev-runtime-103/9421/2.
This documentation should include which storage prefix filter to use in order to test only specific things and not download the whole web of trust if not necessary.