Bump SemVer after parallelized remote externality retrieval update (#131

)

After #130, docs need to be updated, and the `README` regenerated. This
also bumps the version to `0.10.1`

Update to latest polkadot-sdk master (#130)

This includes the remote externalities changes for parallel connection
to RPC servers for faster state downloads.

Fix build-release-binaries workflow by switching from musl to glibc t…

…arget (#128)

Fixes the broken `build-release-binaries.yaml` workflow that was failing
due to C++ standard library conflicts when building for
`x86_64-unknown-linux-musl`.

## Changes
- Switched Linux target from `x86_64-unknown-linux-musl` to
`x86_64-unknown-linux-gnu`
- Removed `.cargo/config.toml` (no longer needed without musl)
- Simplified Linux build dependencies (removed musl-specific packages)
- Added Multi-Block Migration (MBM) documentation to source code to
satisfy `doc` job in CI (left broken in #127)
- Updated README with MBM notes and fixed broken links (also because of
`doc` CI job)

## Why?
The musl build was failing because RocksDB (a C++ dependency) couldn't
link correctly with both libstdc++ and libc++ simultaneously. The glibc
target builds cleanly and produces binaries compatible with all major
Linux distributions.

## Trade-offs
- **Lost**: Static linking (musl benefit)
- **Gained**: Working builds, compatibility with 99% of Linux users

Add support for relay-parent-offset. (#122)

Recently CI fails regularly on runtimes repo because try-runtime does
not yet support runtimes with RP offset.

Changes:
- Use polkadot-sdk master (sadly stable2512 does not contain rp_offset
field yet)
- Fetch rp offset from runtime and add it to inherent
- Simplify inherent usage

---------

Co-authored-by: Bastian Köcher <git@kchr.de>

Inherents and empty block production overhaul (#86)

A pre-requisite to producing empty blocks for MBMs is fixing inherents
for relay and parachains, and moving block production logic from being
tied to `fast_forward` to common logic.

It will also be very beneficial to allow producing blocks based on a
snapshot, without any live node (`--block-ws-uri`).

Based on the changes in this PR, I'll add MBM support to the
`on-runtime-upgrade` subcommand.

- Fixes inherent providers for relay and parachains
- Introduces a SMART inherent provider designed to work across different
chains, removing the requirement for a cli arg to specify which
inherents to use
- Moves inherent and block production to a common utils dir
- Removes requirement for a remote node to produce empty blocks
- Closes #32 (no longer compiles kitchensink runtime)

---------

Co-authored-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>

ci: add apple build target

Expose `snapshot-path` arg (#80)

Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
Co-authored-by: Liam Aharon <liam.aharon@hotmail.com>

Add flag to see storage diff if idemptotent check fails (#78)

When the idempotent migration check fails, users see this unhelpful
error message:

```
❌ Migrations are not idempotent. Selectively remove migrations from Executive until you find the culprit.
```

This PR implements a flag to enable printing the differences in storage.
It is disabled by default because users can ignore the "idempotent"
warning if they want to. If the flag is disabled there is a log that
suggests enabling it, improving the old message.

![Captura desde 2024-02-20
13-59-48](https://github.com/paritytech/try-runtime-cli/assets/44604217/1ae51887-6d26-411a-8874-23924b5cb536)

---------

Co-authored-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
Co-authored-by: Liam Aharon <liam.aharon@hotmail.com>

Fix `TrieError(InvalidStateRoot(...))` error log when runtime upgrade…

… PoV is empty (#77)

Closes #76