This PR enables the `chainSpec_v1` class for the polkadot-parachian. 
The chainSpec is part of the rpc-v2 which is spec-ed at:
https://github.com/paritytech/json-rpc-interface-spec/blob/main/src/api/chainSpec.md.

This also paves the way for enabling a future `chainSpec_unstable_spec`
on all nodes.

Closes: https://github.com/paritytech/polkadot-sdk/issues/5191

cc @paritytech/subxt-team

---------

Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>

Added a new adapter to xcm-builder, the `SingleAssetExchangeAdapter`.
This adapter makes it easy to use `pallet-asset-conversion` for
configuring the `AssetExchanger` XCM config item.

I also took the liberty of adding a new function to the `AssetExchange`
trait, with the following signature:

```rust
fn quote_exchange_price(give: &Assets, want: &Assets, maximal: bool) -> Option<Assets>;
```

The signature is meant to be fairly symmetric to that of
`exchange_asset`.
The way they interact can be seen in the doc comment for it in the
`AssetExchange` trait.

This is a breaking change but is needed for
https://github.com/paritytech/polkadot-sdk/pull/5131.
Another idea is to create a new trait for this but that would require
setting it in the XCM config which is also breaking.

Old PR: https://github.com/paritytech/polkadot-sdk/pull/4375.

---------

Co-authored-by: Adrian Catangiu <adrian@parity.io>

This PR replaces env_logger with sp_tracing because of an issue with
env_logger and gum #4660

---------

Co-authored-by: Adrian Catangiu <adrian@parity.io>
Co-authored-by: Andrei Eres <eresav@me.com>

As the release branch name changed starting from this release, this PR
adds it to the sync templates flow so that checkout step worked
properly.

---------

Co-authored-by: rzadp <roopert7@gmail.com>

This PR reduces the occurrences for identified observed addresses.

Litep2p discovers its external addresses by inspecting the
`IdentifyInfo::ObservedAddress` field reported by other peers.
After we get 5 confirmations of the same external observed address (the
address the peer dialed to reach us), the address is reported through
the network layer.

The PR effectively changes this from 5 to 2.
This has a subtle implication on freshly started nodes for the
authority-discovery discussed below.

The PR also makes the authority discovery a bit more robust by not
publishing records if the node doesn't have addresses yet to report.
This aims to fix a scenario where:
- the litep2p node has started, it has some pending observed addresses
but less than 5
- the authorit-discovery publishes a record, but at this time the node
doesn't have any addresses discovered and the record is published
without addresses -> this means other nodes will not be able to reach us

Next Steps
- [ ] versi testing

Closes: https://github.com/paritytech/polkadot-sdk/issues/5147

cc @paritytech/networking

---------

Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
Co-authored-by: Bastian Köcher <git@kchr.de>

The test name is `test-frame-ui` I don't know if I can also change it to
`test-ui` without breaking other stuff. So I kept the name unchanged.

---------

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

As per #3326, removes usage of the `pallet::getter` macro from the
balances pallet. The syntax `StorageItem::<T, I>::get()` should be used
instead.

Also, adds public functions for compatibility.

cc @muraca

polkadot address: 5GsLutpKjbzsbTphebs9Uy4YK6gTN47MAaz6njPktidjR5cp

---------

Co-authored-by: Bastian Köcher <git@kchr.de>
Co-authored-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>

This PR reverts the removal of an [`if`
statement](https://github.com/paritytech/polkadot-sdk/commit/7ecf3f75#diff-8bf31ba8d9ebd6377983fd7ecc7f4e41cb1478a600db1a15a578d1ae0e8ed435L370)
merged recently, which affected test output verbosity of several pallets
(e.g. staking, EPM, and potentially others).

More generally, the `UnixTime::now` implementation of the timestamp
pallet should log an error *only* when called at the genesis block.

Adds a snapshot step to the try-runtime check that tries to download a
cached snapshot.
The cache is valid for the current day and is otherwise re-created.

Check is now only limited by build time and docker startup.

![Screenshot 2024-07-30 at 02 02
58](https://github.com/user-attachments/assets/0773e9b9-4a52-4572-a891-74b9d725ba70)

![Screenshot 2024-07-30 at 02 02
20](https://github.com/user-attachments/assets/4685ef17-a04c-4bdc-9d61-311d0010f71c)

---------

Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>

This PR backports regular version bumps and reorganisation of the
`prdoc` files from the stable release branch back to master

[subsystem-benchmark] Update availability-distribution-regression-bench baseline after recent subsystem changes (#5180)

ISSUE
Link to the issue:
https://github.com/paritytech/polkadot-sdk/issues/3326

Deliverables

[Deprecation] remove pallet::getter usage from pallet-proxy

---------

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

As per #3326, removes pallet::getter macro usage from the
election-provider-multi-phase pallet. The syntax `StorageItem::<T,
I>::get()` should be used instead.

cc @muraca

---------

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

Add the possibility of injecting session-keys in genesis for
non-validators. Currently all keys injected in genesis were considered
as part of the initial validators set, this PR allows to inject a new
vector with non-authority keys

---------

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

Bumps the known_good_semver group with 1 update:
[serde_json](https://github.com/serde-rs/json).

Updates `serde_json` from 1.0.120 to 1.0.121
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/serde-rs/json/releases">serde_json's
releases</a>.</em></p>
<blockquote>
<h2>v1.0.121</h2>
<ul>
<li>Optimize position search in error path (<a
href="https://redirect.github.com/serde-rs/json/issues/1160">#1160</a>,
thanks <a
href="https://github.com/purplesyringa"><code>@​purplesyringa</code></a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/serde-rs/json/commit/eca2658a22cb39952783cb6914eb18242659f66a"><code>eca2658</code></a>
Release 1.0.121</li>
<li><a
href="https://github.com/serde-rs/json/commit/b0d678cfb473386830d559b6ab255d9e21ba39c5"><code>b0d678c</code></a>
Merge pull request <a
href="https://redirect.github.com/serde-rs/js...

An attempt to improve [the
docs](https://paritytech.github.io/polkadot-sdk/master/polkadot_sdk_docs/index.html)
by applying various corrections:

- grammar/stylistics,
- formatting,
- broken links,
- broken markdown table,
- outdated vscode setting name,
- typos,
- consistency,
- etc.

Part of https://github.com/paritytech/eng-automation/issues/10

Close https://github.com/paritytech/polkadot-sdk/issues/3076

The fix is really just that older messages are replaced if the client
can't keep up with the server instead.
Because I wanted the same functionality as `pipe_from_stream` for both
pending/subscription I added two wrapper types on-top of the types from
jsonrpsee to make it nicer.

I added a trait `Buffer` so I could still use pipe_from_stream but that
abstraction is a little leaky but only to avoid adding an identical
method/function with another strategy...

This is part of the work to further optimize the approval subsystems, if
you want to understand the full context start with reading
https://github.com/paritytech/polkadot-sdk/pull/4849#issue-2364261568,

# Description

This PR contain changes to make possible the run of multiple instances
of approval-distribution, so that we can parallelise the work. This does
not contain any functional changes it just decouples the subsystem from
the subsystem Context and introduces more specific trait dependencies
for each function instead of all of them requiring a context.

It does not have any dependency of the follow PRs, so it can be merged
independently of them.

---------

Signed-off-by: Alexandru Gheorghe <alexandru.gheorghe@parity.io>

Bumps [bs58](https://github.com/Nullus157/bs58-rs) from 0.5.0 to 0.5.1.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/Nullus157/bs58-rs/blob/main/CHANGELOG.md">bs58's
changelog</a>.</em></p>
<blockquote>
<h2>0.5.1 - 2024-03-19</h2>
<ul>
<li>Make it possible to decode in <code>const</code>-context (by <a
href="https://github.com/joncinque"><code>@​joncinque</code></a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/Nullus157/bs58-rs/commit/7d3c9282d2595612e5474df93dd0e017db9b684f"><code>7d3c928</code></a>
Merge pull request <a
href="https://redirect.github.com/Nullus157/bs58-rs/issues/116">#116</a>
from joncinque/const</li>
<li><a
href="https://github.com/Nullus157/bs58-rs/commit/d3fb50ebad42ff34454e3b49c9e93e85df08d835"><code>d3fb50e</code></a>
Merge pull request <a
href="https://redirect.github.com/Nullus157/bs58-rs/issues/117">#117</a>
from Nemo157/criterion-update</li>
<li><a
href="https://github.com/Nullus157/bs58-rs/commit/9038a36ae66f0f5d2b74f7a4f3a630873c71d0a1"><code>9038a36</code></a>
Update dependencies</li>
<li><a
href="https://github.com/Nullus157/bs58-rs/commit/13af427722e681d1ba9c922380663eea2f865d4d"><code>13af427</code></a>
Update criterion to fix cargo-deny issues</li>
<li><a
href="https://github.com/Nullus157/bs58-rs/commit/b6ad26a72010dec7caf18cf4cb4e1e7131ef57e6"><code>b6ad26a</code></a>
Prepare to release 0.5.1</li>
<li><a
href="https://github.com/Nullus157/bs58-rs/commit/e18e057bf86e67e028ed6da0ee4f1850978d2301"><code>e18e057</code></a>
Move const-compatible API onto <code>decode::DecodeBuilder</code>
directly</li>
<li><a
href="https://github.com/Nullus157/bs58-rs/commit/e65bfa72a23c57fbc05cad66c9b667c6eae946fa"><code>e65bfa7</code></a>
decode: Add const-compatible decoder</li>
<li><a
href="https://github.com/Nullus157/bs58-rs/commit/2b0d73b9955f6a745f9b6fbb387bba2b96ea89fd"><code>2b0d73b</code></a>
Merge pull request <a
href="https://redirect.github.com/Nullus157/bs58-rs/issues/113">#113</a>
from Nemo157/cli-version-bump</li>
<li><a
href="https://github.com/Nullus157/bs58-rs/commit/be42edf49589d3f5135871ab129bfff4ded21d67"><code>be42edf</code></a>
Prepare for 0.1.2 cli release</li>
<li><a
href="https://github.com/Nullus157/bs58-rs/commit/6bdc4b2c673f334de0dd316f2e7d988d0db5cb52"><code>6bdc4b2</code></a>
Merge pull request <a
href="https://redirect.github.com/Nullus157/bs58-rs/issues/112">#112</a>
from Nemo157/cli-dep-update</li>
<li>Additional commits viewable in <a
href="https://github.com/Nullus157/bs58-rs/compare/0.5.0...0.5.1">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=bs58&package-manager=cargo&previous-version=0.5.0&new-version=0.5.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

[pallet_contracts] Modify the storage host function benchmarks to run on an unbalanced storage trie. (#5036)

This PR modifies the storage host function benchmarks. Previously, they
were run on an empty storage trie.
Now, they are run on an unbalanced storage trie to reflect worst case
scenario.
This approach increases the storage host function weights and decreases
the probability of DoS attacks.

---------

Co-authored-by: command-bot <>
Co-authored-by: PG Herveou <pgherveou@gmail.com>

Bumps [ref-cast](https://github.com/dtolnay/ref-cast) from 1.0.20 to
1.0.23.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/dtolnay/ref-cast/releases">ref-cast's
releases</a>.</em></p>
<blockquote>
<h2>1.0.23</h2>
<ul>
<li>Resolve unexpected_cfgs warning (<a
href="https://redirect.github.com/dtolnay/ref-cast/issues/47">#47</a>)</li>
</ul>
<h2>1.0.22</h2>
<ul>
<li>Update proc-macro2 to fix caching issue when using a rustc-wrapper
such as sccache</li>
</ul>
<h2>1.0.21</h2>
<ul>
<li>Support <code>forbid(unsafe_code)</code> (<a
href="https://redirect.github.com/dtolnay/ref-cast/issues/45">#45</a>,
thanks <a href="https://github.com/yuja"><code>@​yuja</code></a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/dtolnay/ref-cast/commit/06c520cd555920951cc1939fcb0c5d855b61134c"><code>06c520c</code></a>
Release 1.0.23</li>
<li><a
href="https://github.com/dtolnay/ref-cast/commit/fd3256dcce6afe7204792f09fc8b227b208b00fc"><code>fd3256d</code></a>
Merge pull request <a
href="https://redirect.github.com/dtolnay/ref-cast/issues/47">#47</a>
from dtolnay/checkcfg</li>
<li><a
href="https://github.com/dtolnay/ref-cast/commit/473dc818a94318524a56600891e50d181e3d6b8a"><code>473dc81</code></a>
Resolve unexpected_cfgs warning</li>
<li><a
href="https://github.com/dtolnay/ref-cast/commit/b4d78e28708129fcc413cbd1555b95f542d40551"><code>b4d78e2</code></a>
Revert &quot;Temporarily disable miri on doctests&quot;</li>
<li><a
href="https://github.com/dtolnay/ref-cast/commit/24de24e13da1cc179f1646fd078dee36b288f4ff"><code>24de24e</code></a>
Resolve legacy_numeric_constants clippy lints</li>
<li><a
href="https://github.com/dtolnay/ref-cast/commit/33b0b8f8a40a501345551a97bde7951cc0e93564"><code>33b0b8f</code></a>
Update ui test suite to nightly-2024-03-31</li>
<li><a
href="https://github.com/dtolnay/ref-cast/commit/bd301af5205224a5670e460e8bc94ecff2a3ca66"><code>bd301af</code></a>
Explicitly install a Rust toolchain for cargo-outdated job</li>
<li><a
href="https://github.com/dtolnay/ref-cast/commit/b747bf79ed48d3138ccb8fa2a88bbff9bed56ad2"><code>b747bf7</code></a>
Temporarily disable miri on doctests</li>
<li><a
href="https://github.com/dtolnay/ref-cast/commit/0b59588839a5725f942b44eed94ff0a5f2e1477f"><code>0b59588</code></a>
Raise minimum tested compiler to 1.70</li>
<li><a
href="https://github.com/dtolnay/ref-cast/commit/ad5cadba6b700bb3647ef0f31954f55ef27d4fc1"><code>ad5cadb</code></a>
Update ui test suite to nightly-2024-03-06</li>
<li>Additional commits viewable in <a
href="https://github.com/dtolnay/ref-cast/compare/1.0.20...1.0.23">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=ref-cast&package-manager=cargo&previous-version=1.0.20&new-version=1.0.23)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Fix https://github.com/paritytech/polkadot-sdk/issues/3487.

---------

Co-authored-by: Dmitry Lavrenov <39522748+dmitrylavrenov@users.noreply.github.com>
Co-authored-by: Bastian Köcher <info@kchr.de>
Co-authored-by: Bastian Köcher <git@kchr.de>

Bumps the ci_dependencies group with 5 updates:

| Package | From | To |
| --- | --- | --- |
| [actions/checkout](https://github.com/actions/checkout) | `2` | `4` |
| [actions/cache](https://github.com/actions/cache) | `3.3.3` | `4.0.2`
|
| [actions/setup-python](https://github.com/actions/setup-python) | `2`
| `5` |
|
[actions/download-artifact](https://github.com/actions/download-artifact)
| `4.1.4` | `4.1.8` |
|
[docker/setup-buildx-action](https://github.com/docker/setup-buildx-action)
| `3.0.0` | `3.5.0` |

Updates `actions/checkout` from 2 to 4
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/actions/checkout/releases">actions/checkout's
releases</a>.</em></p>
<blockquote>
<h2>v4.0.0</h2>
<h2>What's Changed</h2>
<ul>
<li>Update default runtime to node20 by <a
href="https://github.com/takost"><code>@​takost</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/1436">actions/checkout#14...

I made mistake on previous PR
https://github.com/paritytech/polkadot-sdk/pull/5150. It disabled all
unexpected cfgs instead of just allowing `substrate_runtime` condition.

In this PR: unexpected cfgs other than `substrate_runtime` are still
checked. and some warnings appear about them

Bumps [spinners](https://github.com/fgribreau/spinners) from 4.1.0 to
4.1.1.
<details>
<summary>Commits</summary>
<ul>
<li>See full diff in <a
href="https://github.com/fgribreau/spinners/commits">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=spinners&package-manager=cargo&previous-version=4.1.0&new-version=4.1.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase t...

A bit of a controversial move, but a good preparation for even further
reducing the traffic on outdated content of `substrate.io`. Current
status:

<img width="728" alt="Screenshot 2024-07-15 at 11 32 48"
src="https://github.com/user-attachments/assets/df33b164-0ce7-4ac4-bc97-a64485f12571">

Previously, I was in favor of changing the domain of the rust-docs to
something like `polkadot-sdk.parity.io` or similar, but I think the
current format is pretty standard and has a higher chance of staying put
over the course of time:

`<org-name>.github.io/<repo-name>` ->
`https://paritytech.github.io/polkadot-sdk/`

part of https://github.com/paritytech/eng-automation/issues/10

The problem with the current implementation is that minting will cause
the region coremask to be set to `Coremask::complete` regardless of the
actual coremask.

This PR fixes that.

More details about the nonfungible implementation can be found here:
https://github.com/paritytech/polkadot-sdk/pull/3455

---------

Co-authored-by: Dónal Murray <donalm@seadanda.dev>
Co-authored-by: Branislav Kontur <bkontur@gmail.com>
Co-authored-by: Francisco Aguirre <franciscoaguirreperez@gmail.com>
Co-authored-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>

Fix warnings for rust 1.80

Related to https://github.com/paritytech/polkadot-sdk/issues/5144, plus
remove the lines of code badge as it was not working.

This should prevent excessive pinning of blocks while we are waiting for
the block ancestry to be downloaded after gap sync.
We spawn a new task that gets polled to transform finality notifications
into an unpinned counterpart. Before this PR, finality notifications
were kept in the notification channel. This led to pinning cache
overflows.

fixes #4389

---------

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

Previously, we were checking if the relay parent of a new candidate does
not move backwards from the latest included on-chain candidate. This was
fine prior to elastic scaling. We now need to also check that the relay
parent progresses from the latest pending availability candidate, as
well as check the progression within the candidate chain in the inherent
data.

Prospective-parachains is already doing this check but we should also
add it in the runtime

# Description
This is continue of the work to backport
`emulated-integration-tests-common`, if you want to understand the full
context start with reading
[#4930](https://github.com/paritytech/polkadot-sdk/pull/4930)

This should make it possible to use the umbrella crate alone for
templates/*/runtime crate of the repo

This will fix the compilation on the latest Rust 1.80.0

PS. There are tons of new warnings about feature gates and annotations,
it would be nice you guys to investigate them

- Prevent `major` changes to be merged into a `stable` branch.
- Place a comment on backport MRs to provide context of what it means.

Comment looks like this:

![Screenshot 2024-07-24 at 17 36
35](https://github.com/user-attachments/assets/6393549b-7b15-41e5-a804-8581c625ceff)

---------

Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>

We may want to construct a `Footprint` by taking the `max_encoded_len`
of a type, without having to construct the type.

This impl allows easy access to that.

---------

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

Bumps [walkdir](https://github.com/BurntSushi/walkdir) from 2.4.0 to
2.5.0.
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/BurntSushi/walkdir/commit/4f26be4d450910916ea11533b2efc52b9a6483bc"><code>4f26be4</code></a>
2.5.0</li>
<li><a
href="https://github.com/BurntSushi/walkdir/commit/3be5734033b20c2476e6ca9154c3bb0e0ed840b2"><code>3be5734</code></a>
api: implement <code>FusedIterator</code></li>
<li><a
href="https://github.com/BurntSushi/walkdir/commit/b0d16b759a59836756f8d0ec637f7f8d121a48cd"><code>b0d16b7</code></a>
ci: fix it</li>
<li>See full diff in <a
href="https://github.com/BurntSushi/walkdir/compare/2.4.0...2.5.0">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=walkdir&package-manager=cargo&previous-version=2.4.0&new-version=2.5.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependab...

Since we have a minimal template, I propose enhancing the solochain
template, which would be easier for startup projects.

- Sync separates `api`, `configs`, and `benchmarks` from the parachain
template
- introducing `frame-metadata-hash-extension`
- Some style update

---------

Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>